--- title: Malomo API Integration on Truto slug: malomo category: E-Commerce canonical: "https://truto.one/integrations/detail/malomo/" --- # Malomo API Integration on Truto **Category:** E-Commerce **Status:** Generally available ## MCP-ready AI tools Truto exposes 21 tools for Malomo that AI agents can call directly. - **list_all_malomo_orders** — List malomo orders with optional filters. Returns: id, alternate_id, email, number, customer, shipments, created_at, updated_at, meta. Filter by alternate_id, tracking_code, number, or customer_email. - **get_single_malomo_order_by_id** — Get a single malomo order by id. Returns: id, alternate_id, email, number, customer, shipments, created_at, updated_at, meta. Required: id. - **create_a_malomo_order** — Create a new order in malomo. Returns: id, alternate_id, email, number, customer, shipments, created_at, updated_at, meta. - **update_a_malomo_order_by_id** — Update a malomo order by id. Returns: id, alternate_id, email, number, customer, shipments, created_at, updated_at, meta. Required: id. The shipments field must be a complete list — any existing carrier/tracking_code pairs not included will be removed. - **delete_a_malomo_order_by_id** — Delete a malomo order by id. Returns an empty 204 response on success. Required: id. - **list_all_malomo_customers** — List customers in malomo. Returns: id, email, first_name, last_name, phone_number, created_at, updated_at. - **get_single_malomo_customer_by_id** — Get a single malomo customer by id. Returns: id, email, first_name, last_name, phone_number, created_at, updated_at. Required: id. - **create_a_malomo_customer** — Create a new customer in malomo. Returns: id, email, first_name, last_name, phone_number, created_at, updated_at. - **update_a_malomo_customer_by_id** — Update an existing malomo customer by id. Returns: id, email, first_name, last_name, phone_number, created_at, updated_at. Required: id. - **delete_a_malomo_customer_by_id** — Delete a malomo customer by id. Returns an empty 204 response on success. Required: id. - **create_a_malomo_webhook** — Create a new Malomo webhook to receive event notifications. Returns: id, active, topic, url, created_at, updated_at. - **list_all_malomo_webhooks** — List all Malomo webhooks. Returns: id, active, topic, url, created_at, updated_at. - **get_single_malomo_webhook_by_id** — Get a single Malomo webhook by id. Returns: id, active, topic, url, created_at, updated_at. Required: id. - **update_a_malomo_webhook_by_id** — Update an existing Malomo webhook by id. Returns: id, active, topic, url, created_at, updated_at. Required: id. - **delete_a_malomo_webhook_by_id** — Delete a Malomo webhook by id. Returns an empty 204 response on success. Required: id. - **get_single_malomo_orders_by_alternate_id_by_id** — Get a malomo order by its alternate ID. Returns: id, alternate_id. Required: alternate_id. - **get_single_malomo_orders_by_tracking_code_by_id** — Get malomo orders by tracking code. Returns: tracking_code. Required: tracking_code. - **get_single_malomo_orders_by_number_by_id** — Get malomo orders filtered by order number or customer email. Returns: number, customer_email. - **list_all_malomo_order_events** — List all events for a specific order in malomo. Returns: id, order_id. Required: order_id. - **create_a_malomo_order_event** — Create a new event for a specific order in malomo. Returns: id, order_id. Required: order_id. - **list_all_malomo_customer_events** — List events for a malomo customer. Returns a collection of event records including id. Required: customer_id. ## How it works 1. **Link your customer's Malomo account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Malomo.** The Proxy API is a 1-to-1 mapping of the Malomo API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Trigger lifecycle messages from delivery milestones** — SMS, email, and review platforms can subscribe to Malomo order events to send perfectly timed messages when packages are out for delivery, delivered, or delayed — instead of guessing based on fulfillment timestamps. - **Deflect WISMO tickets inside support tools** — Helpdesk and chat platforms can look up a shopper's latest order and tracking status by email, order number, or tracking code, then surface it directly in the agent console to resolve 'where is my order?' inquiries without context switching. - **Sync orders from custom fulfillment stacks** — ERPs, OMS, and headless commerce platforms can push orders and shipments into Malomo so merchants get branded tracking pages even for orders that never touched Shopify. - **Inject custom milestones into the tracking timeline** — QA, personalization, and packaging SaaS can write custom order events into Malomo (e.g., 'Quality Check Passed', 'Gift Wrapped') so they appear natively on the merchant's branded tracking page. - **Automate proactive resolution for damaged or lost shipments** — Returns, warranty, and shipping protection platforms can listen for problem events and trigger replacement orders or claims workflows before the customer ever files a complaint. ## What you can build - **Auto-provisioned webhook subscriptions** — On install, programmatically create Malomo webhooks for the topics your product needs so merchants never have to configure anything in the Malomo UI. - **Multi-key order lookup widget** — A support sidebar that resolves orders via tracking code, order number, or alternate ID to match Malomo records against tickets, chats, or CRM contacts. - **Delivery-aware campaign triggers** — A rules engine in your marketing or review tool that fires actions based on real-time Malomo order events like Delivered, Out for Delivery, or Delayed. - **Custom tracking timeline events** — Let your users publish branded milestones from your platform — like 'Personalization Complete' or 'Inspected' — directly onto the Malomo tracking page using order event creation. - **Order and shipment sync from external systems** — Push new orders and tracking codes from an ERP, 3PL, or headless storefront into Malomo so every shipment gets a branded tracking experience. - **Safe shipment array updates** — A fulfillment workflow that fetches the current order, appends new carrier/tracking pairs, and writes the full shipments array back — avoiding accidental deletion of existing tracking records. ## FAQs ### How does authentication work for connecting a merchant's Malomo account? Your end users authenticate their Malomo account through Truto's connection flow. Truto handles credential storage, refresh, and per-tenant isolation, so your application code never touches Malomo API keys directly. ### Can I receive real-time Malomo events instead of polling? Yes. You can use the create_a_malomo_webhook tool to programmatically register webhook subscriptions on behalf of the merchant, then receive events like order updates and shipment milestones through Truto's event pipeline. ### How do I look up a Malomo order if I don't have its internal ID? Malomo exposes dedicated lookup endpoints by order number, tracking code, and alternate ID. Truto surfaces these as get_single_malomo_orders_by_number_by_id, get_single_malomo_orders_by_tracking_code_by_id, and get_single_malomo_orders_by_alternate_id_by_id. ### What happens when I update a Malomo order with a new tracking code? Malomo treats the shipments array as the source of truth on update — any carrier/tracking_code pairs you omit will be removed. Always fetch the current order first, append the new shipment, and submit the complete array back via update_a_malomo_order_by_id. ### Can I add my own events to the Malomo tracking timeline? Yes. The create_a_malomo_order_event tool lets you inject custom milestones into an order's event stream, which Malomo renders alongside native carrier events on the merchant's branded tracking page. ### What Malomo objects can I read and write through Truto today? The current toolset covers orders (CRUD plus lookups by number, tracking code, and alternate ID), customers (CRUD), webhooks (CRUD), order events (list and create), and customer events (list). Anything beyond this can be added on request. ## Related reading - [Connect Malomo to Claude: Sync Shipment Tracking & Webhooks](https://truto.one/blog/connect-malomo-to-claude-sync-shipment-tracking-webhooks/) — Learn how to connect Malomo to Claude using a managed MCP server. Automate shipment tracking, webhook configuration, and order management with AI agents. - [Connect Malomo to ChatGPT: Manage Orders, Customers & Events](https://truto.one/blog/connect-malomo-to-chatgpt-manage-orders-customers-events/) — A complete engineering guide to generating a managed Malomo MCP server using Truto. Learn how to connect Malomo to ChatGPT for order and event automation. - [Connect Malomo to AI Agents: Automate Fulfillment & Order Data](https://truto.one/blog/connect-malomo-to-ai-agents-automate-fulfillment-order-data/) — Learn how to connect Malomo to AI agents using Truto's /tools endpoint. Automate order fulfillment, shipment tracking, and customer events without custom wrappers.