E-Commerce

Malomo
API integration

Ship E-Commerce features without building the integration. Full Malomo API access via Proxy and 20+ MCP-ready tools for AI agents — extend models and mappings to fit your product.

Talk to us

Use Cases

Why integrate with Malomo

Common scenarios for SaaS companies building Malomo integrations for their customers.

01

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.

02

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.

03

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.

04

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.

05

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

Ship these features with Truto + Malomo

Concrete product features your team can ship faster by leveraging Truto’s Malomo integration instead of building from scratch.

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.

SuperAI

Malomo AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

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.

Why Truto

Why use Truto’s MCP server for Malomo

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 500+ integrations.

01

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

02

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

03

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

04

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

05

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

06

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

How It Works

From zero to integrated

Go live with Malomo in under an hour. No boilerplate, no maintenance burden.

01

Link your customer’s Malomo account

Use Truto’s frontend SDK to connect your customer’s Malomo account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

02

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

03

Call our API, we call Malomo

Truto’s Proxy API is a 1-to-1 mapping of the Malomo API. You call us, we call Malomo, and pass the response back in the same cycle.

04

Unified response format

Every response follows a single format across all integrations. We translate Malomo’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Malomo on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

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.

From the Blog

Malomo integration guides

Deep dives, architecture guides, and practical tutorials for building Malomo integrations.

MalomoAPI integration