Skip to content

E-Commerce · Beta

Monta
API integration

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

Built for specific customer use cases. Issues are resolved quickly.

Talk to us
Monta

Use Cases

Why integrate with Monta

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

01

Embed 3PL fulfillment visibility in your e-commerce OS

If you sell an order management, ERP, or e-commerce dashboard to European D2C brands, Monta is the fulfillment backbone many of them rely on. Offering a native Monta integration via Truto lets your users sync orders, stock, and shipment statuses without leaving your product.

02

Power WISMO automation inside support platforms

Helpdesk and AI support SaaS vendors can resolve 'where is my order' tickets automatically by pulling live order progress, processing timeframes, and shipping labels from Monta. This removes the need for agents to log into the Monta portal to answer routine questions.

03

Automate cross-border returns for RMA platforms

Returns SaaS can create return forecasts in Monta the moment a shopper initiates an RMA, generate return labels, and watch the warehouse inspection status to trigger refunds automatically. Truto lets you ship this to every Monta-using merchant without maintaining the connector yourself.

04

Close the loop between procurement and warehouse receipt

Demand planning and procurement tools can push inbound forecasts to Monta when POs are issued and monitor inbound arrivals to know exactly when stock becomes sellable. This turns a blind spot in the supply chain into a real-time signal for ads, pricing, and reorder logic.

05

Keep storefronts and marketplaces in sync with real stock

Multi-channel listing tools can poll Monta product stock and product events to ensure Shopify, Amazon, and other channels never oversell. Truto handles the polling, pagination, and auth so you only consume clean data.

What You Can Build

Ship these features with Truto + Monta

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

01

Bi-directional order sync

Create new orders in Monta, update or cancel in-flight orders with mandatory reasoning, and split orders when fulfillment logic requires it.

02

Reliable event-feed ingestion

Consume Monta's cursor-based order and product event feeds to track every status change (printed, picked, shipped, returned) without missing updates during downtime.

03

Inbound forecast automation

Push purchase orders into Monta as inbound forecasts and forecast groups so warehouse staff are prepared for incoming pallets at the SKU and quantity level.

04

End-to-end returns workflow

Create return forecasts, fetch PDF return labels, track return label history, and update return and return-line statuses to drive refund automation.

05

Live stock and product catalog management

List, create, update, and delete products, manage product groups and rules, apply stock mutations, and look up SKUs for real-time inventory accuracy.

06

GDPR-compliant order anonymization

Expose a one-click 'right to be forgotten' action that triggers Monta's order anonymization endpoint to strip PII from shipping records.

07

Shipping label operations

Create, retrieve, cancel, void, and bulk-cancel shipping labels, and download the label file directly inside your UI.

SuperAI

Monta AI agent tools

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

monta_addresses_validate

Validate a delivery address. Required: City, CountryCode, Street.

get_single_monta_batch_by_id

Get batch with guid. Required: id.

list_all_monta_health_checks

Check that the Monta API is up.

list_all_monta_inbound_forecast_events

List inbound forecast events after a given event id. Required: since_id.

list_all_monta_inbound_forecast_group_labels

Download a delivery label for a forecastgroup based on reference. Required: reference. Returns a file (PDF), not JSON.

get_single_monta_inbound_forecast_group_by_id

Get an entire inbound forecast group by its reference or by its unique id (GUID). Required: id.

update_a_monta_inbound_forecast_group_by_id

Update an existing inbound forecast group based on reference. Required: id.

delete_a_monta_inbound_forecast_group_by_id

Delete an entire inbound forecast group, including inbound forecasts. Required: id.

list_all_monta_inbound_forecast_groups

Retrieve details of multiple forecast groups based on several optional parameters. The connector pages through all results.

create_a_monta_inbound_forecast_group

Create a new inbound forecast group based on reference. Required: InboundForecasts, Reference.

get_single_monta_inbound_forecast_by_id

Retrieve details of a single forecast from group with reference and this specific sku. Required: id, reference.

update_a_monta_inbound_forecast_by_id

Update an existing inbound forecast in an existing inbound forecast group. Required: id, reference, Quantity.

delete_a_monta_inbound_forecast_by_id

Delete a single inbound forecast from an inbound forecast group. Required: id, reference.

create_a_monta_inbound_forecast

Create a new inbound forecast in an existing inbound forecast group. Required: reference, Quantity, Sku.

list_all_monta_inbound_forecasts

List all inbound forecasts for a product SKU. Required: product_sku.

monta_inbound_forecasts_bulk_approve

Approve multiple inbound forecasts at once based on ID.

list_all_monta_inbounds

Reads all inbounds.

create_a_monta_order_anonymization

Anonymize an order (GDPR forget): removes the invoice and/or shipping personal data. Required: webshop_order_id.

list_all_monta_order_batches

Get order with batches. Required: webshop_order_id.

create_a_monta_order_colli

Create colli for order. Required: webshop_order_id, Number.

list_all_monta_order_colli

Get order collies. Required: webshop_order_id.

list_all_monta_order_deleted_lines

Get order deleted lines. Required: webshop_order_id.

list_all_monta_order_event_feed

List order events after a given event id (an event feed across all orders). Required: since_id. Monta returns the next 200 events per call: call again with the last event id until fewer than 200 come back.

list_all_monta_order_events

Get order events. Required: webshop_order_id.

list_all_monta_order_headers

List orders with header data only (lighter than orders.list), 30 per page. The connector pages through all results.

list_all_monta_order_origins

List the order origins (shops) with their shipper and surprise options.

list_all_monta_order_processing_timeframes

Get expected processing timeframe. Required: webshop_order_id.

list_all_monta_order_return_forecasts

Get return forecasts for order. Required: webshop_order_id.

list_all_monta_order_return_labels

Get return labels for order. Required: webshop_order_id.

list_all_monta_order_returns

Get returns for order. Required: webshop_order_id.

create_a_monta_order_rma_link

Create RMA link for an order. Required: webshop_order_id.

list_all_monta_order_serials

Get order with serial numbers. Required: webshop_order_id.

get_single_monta_order_shipping_label_file_by_id

Download shipping label for an order. Required: id, webshop_order_id. Returns a file (PDF), not JSON.

create_a_monta_order_shipping_label

Create shipping label for an order. Required: webshop_order_id.

list_all_monta_order_shipping_labels

Get shipping labels for an order. Required: webshop_order_id.

monta_order_shipping_labels_cancel

Cancel the most recent shipping label of an order. Required: webshop_order_id.

monta_order_shipping_labels_bulk_cancel

Cancel all shipping labels of an order. Required: webshop_order_id.

monta_order_shipping_labels_void

Cancel one shipping label of an order, chosen by its track and trace code. Required: webshop_order_id, track_and_trace.

get_single_monta_order_by_id

Fetches order information for given order ID. Required: id.

update_a_monta_order_by_id

Update an order. Only possible while the order is not picked yet. Required: id.

monta_orders_cancel

Delete (cancel) an order in Monta. Monta requires a Note explaining why. Required: webshop_order_id, Note.

list_all_monta_orders

List orders with full details, 30 per page. The connector pages through all results.

create_a_monta_order

Create a new order. Required: ConsumerDetails, WebshopOrderId.

monta_orders_split

Split an Order. Required: webshop_order_id.

list_all_monta_pick_routes

Fetch pickroute information for your relation (max 100 per call).

delete_a_monta_product_barcode_by_id

Delete barcode from product. Required: id, sku.

monta_product_barcodes_bulk_delete

Delete all barcodes from a product. Required: sku.

list_all_monta_product_events

List product events after a given event id. Required: since_id.

list_all_monta_product_field_definitions

Get all custom field definitions for the current relation.

get_single_monta_product_field_value_by_id

Retrieve custom field values for a specific product. Required: id.

update_a_monta_product_field_value_by_id

Create or update custom field values for a specific product. Required: id.

list_all_monta_product_groups

Get all product groups.

create_a_monta_product_group

Add a product group.

get_single_monta_product_group_by_id

Get product group by ID. Required: id.

monta_product_groups_attach

Add products to a product group. Required: product_group_id.

monta_product_groups_detach

Remove products from a product group. Required: product_group_id.

delete_a_monta_product_group_by_id

Delete a group. Required: id.

list_all_monta_product_images

Retrieve an array of the Images of a product by Sku, as base64 strings. Required: sku.

create_a_monta_product_rule

Create new product rule.

list_all_monta_product_rules

Get all product rules. The connector pages through all results.

get_single_monta_product_rule_by_id

Get product rule by id. Required: id.

update_a_monta_product_rule_by_id

Update product rule. Required: id.

delete_a_monta_product_rule_by_id

Delete product rule. Required: id.

create_a_monta_product_stock_mutation

Change the stock of a product by creating a stock mutation. Required: sku, Comment, Quantity, WarehouseGuid, WarehouseLocationCode.

list_all_monta_product_stocks

Retrieve the stock of a product using sku. Required: sku, include_split_stock.

get_single_monta_product_by_id

Retrieve a product using SKU. Encode a slash in the SKU as %2F. Required: id.

update_a_monta_product_by_id

Update a product using SKU. Encode a slash in the SKU as %2F. Required: id.

delete_a_monta_product_by_id

Delete a product using sku. Encode a slash in the SKU as %2F. Required: id.

monta_products_lookup

For retrieving a product based on the barcode.

create_a_monta_product

Create a new product. Required: Description, Sku.

list_all_monta_products

For the collection of all products. The connector pages through all results.

monta_products_bulk_get

Retrieve multiple products by a list of SKUs.

list_all_monta_purchase_order_groups

List purchase order groups created on or after a date.

list_all_monta_report_files

Download specific report. Required: report_id. Returns a file (binary), not JSON.

list_all_monta_reports

Fetch last 30 reports (after given date).

list_all_monta_return_documents

Get return documents for return. Required: return_id.

list_all_monta_return_forecast_labels

Get return labels for return forecast. Required: code.

create_a_monta_return_forecast

Post new return forecast. Required: Code, WebshopOrderId.

list_all_monta_return_forecasts

Retrieve details of all return forecasts. The connector pages through all results.

get_single_monta_return_forecast_by_id

Get return forecast by code. Required: id.

update_a_monta_return_forecast_by_id

Update return forecast. The return reason of the lines is the only field that can be updated. Required: id, Code, WebshopOrderId.

list_all_monta_return_label_changes

Fetches the first 100 return label changes since a change ID.

list_all_monta_return_label_history

Fetch the change history of a return label. Required: track_and_trace_code.

get_single_monta_return_label_by_id

Fetch a return label by its track and trace code/barcode. Required: id.

create_a_monta_return_line_status

Set the status of one or more lines of a return. Required: return_id.

list_all_monta_return_reasons

Retrieve the returnreasons available in the RMA.

create_a_monta_return_status

Set the status of a whole return. Required: return_id, status.

get_single_monta_return_by_id

Get data for specific return. Required: id.

list_all_monta_returns

List returns created since a date. Required: since. Monta looks back at most 1 day.

monta_shipping_options_lookup

Get the available shipping options for an address and order details. Required: Address, Currency, Language, Origin.

get_single_monta_supplier_by_id

Get supplier by supplier code. Required: id.

update_a_monta_supplier_by_id

Update supplier information. Required: id, Code.

delete_a_monta_supplier_by_id

Delete supplier. Required: id.

list_all_monta_suppliers

Get all suppliers.

create_a_monta_supplier

Create new supplier. Required: Code, Title.

list_all_monta_updated_orders

List orders whose status changed since a date. Required: updated_since.

list_all_monta_updated_product_rules

List product rules changed after a given id. Required: since_id.

list_all_monta_updated_products

List products whose stock changed since a date. Required: updated_since. Monta looks back at most 7 days, and limits this endpoint separately (a bucket of 5 calls, refilled 1 every 10 seconds).

list_all_monta_updated_returns

List returns whose status changed since a date. Required: since. Monta looks back at most 1 day.

list_all_monta_warehouse_order_line_floors

List warehouse order line floors. Required: warehouse_guid.

Why Truto

Why use Truto’s MCP server for Monta

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1050+ 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

Start with Monta in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.

01

Link your customer’s Monta account

Use Truto’s frontend SDK to connect your customer’s Monta 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 Monta

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

04

Unified response format

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

FAQs

Common questions about Monta on Truto

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

How does authentication to Monta work through Truto?

Your end users connect their Monta account through Truto's hosted auth flow. Truto stores and refreshes the credentials, so you make authenticated calls to Monta without handling secrets yourself.

Does Truto support Monta's cursor-based event feeds?

Yes. Endpoints like the order event feed, product events, updated orders, updated products, and updated returns are available, so you can run reliable incremental syncs using Monta's since_id pattern instead of relying on webhooks.

Can we create and manage inbound forecasts for warehouse receiving?

Yes. Truto exposes the full inbound forecast and inbound forecast group lifecycle — create, list, get, update, delete, and bulk approve — plus a list of actual inbounds so you can confirm when stock has physically arrived.

What returns operations are supported?

You can create return forecasts, list and retrieve returns and return labels, pull return label history and changes, list return reasons and documents, and push both return status and return-line status updates to drive refund workflows.

Can we cancel or modify orders after they've been submitted?

Yes. You can update an order, cancel a single order, split an order, and bulk-cancel or void shipping labels. Monta requires a cancellation reason, which you'll pass through the same API call.

How do we handle custom product fields?

Monta exposes product field definitions and product field values as first-class resources. Truto surfaces endpoints to list definitions and get or update individual field values, so you can map merchant-specific attributes without hardcoding.

Is there a way to handle GDPR deletion requests?

Yes. The create order anonymization endpoint is supported, letting you trigger Monta's native 'right to be forgotten' process for a specific order directly from your product.

Monta

Get Monta integrated into your app

Our team understands what it takes to make a Monta integration successful. A short, crisp 30 minute call with folks who understand the problem.