E-Commerce · Beta
Fulfil
API integration
Ship E-Commerce features without building the integration. Full Fulfil API access via Proxy and 50+ 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 usUse Cases
Why integrate with Fulfil
Common scenarios for SaaS companies building Fulfil integrations for their customers.
Launch a native Fulfil integration for your 3PL or WMS platform
Let Fulfil merchants route orders to your warehouse network without custom engineering work on each account. Truto handles auth, pagination, and rate limits so you can focus on the pick-pack-ship workflow logic.
Power AI-driven demand planning and procurement
Pull historical sales orders and live product stock data from your customers' Fulfil accounts to forecast demand and auto-draft purchase orders. Perfect for inventory optimization SaaS serving $10M+ DTC brands.
Embed real-time order and shipment context in CX tools
Give support agents instant visibility into Fulfil sales orders, customer shipments, and tracking status directly inside helpdesk sidebars — no tab switching, no stale data.
Build a returns management platform with accurate restocking
Query original sales orders and customer shipments to generate RMAs, calculate refunds, and push restock updates back into Fulfil without breaking the merchant's ledger.
Offer wholesale and B2B commerce portals on top of Fulfil
Create sales orders and contacts directly in Fulfil for custom B2B storefronts that bypass Shopify, keeping pricing, customer, and order data perfectly aligned with the merchant's ERP.
What You Can Build
Ship these features with Truto + Fulfil
Concrete product features your team can ship faster by leveraging Truto’s Fulfil integration instead of building from scratch.
Two-way shipment sync with workflow-safe state transitions
Fetch pending customer shipments, write tracking numbers and carrier details back, and trigger the `process` method via the execute endpoint so Fulfil properly deducts inventory and posts journal entries.
Automated purchase order drafting
Create draft purchase orders in Fulfil tied to the correct supplier contact, so operations managers only need to review and approve inside their ERP.
Product and SKU master data sync
Keep products, variants, and supplier contacts aligned between your platform and Fulfil using list, create, update, and bulk-update endpoints.
Scheduled report extraction into your BI layer
Discover available Fulfil reports, inspect their schemas, and execute them on a schedule to pipe reconciled financial and inventory data into dashboards.
Custom field-aware data writes
Use Fulfil's model schema endpoint to dynamically discover each merchant's custom fields and allowed values before creating or updating records, so your integration never breaks on customized tenants.
Sales order lifecycle automation
List, create, and update sales orders — and trigger workflow methods like `confirm` via the execute endpoint — to automate order intake from external storefronts or B2B portals.
SuperAI
Fulfil 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_fulfil_contact_counts
Count contact (customer, supplier or other party)s matching an optional where filter. The count is in result.
list_all_fulfil_contacts
List contact (customer, supplier or other party)s with Fulfil's find method: filter with where, pick fields, sort with ordering. The connector follows the cursor through every page.
get_single_fulfil_contact_by_id
Get one contact (customer, supplier or other party) by id (Fulfil's serialize: the server's summary of the record). For specific fields use list with where {"id":
create_a_fulfil_contact
Create one or more contact (customer, supplier or other party)s in a single call. Send the records as params.vlist (an array, even for one record); nested lines are allowed. Returns the new ids. Required: params.
update_a_fulfil_contact_by_id
Update data fields of one contact (customer, supplier or other party). Send the new values as values; change state with execute (a workflow method such as confirm or process), never by writing the state field. Required: id, values.
fulfil_contacts_bulk_update
Write the same values to several contact (customer, supplier or other party)s in one call: send params.ids and params.values. Required: params.
delete_a_fulfil_contact_by_id
Permanently delete one contact (customer, supplier or other party). Required: id.
fulfil_contacts_execute
Call a workflow or other model method on contact (customer, supplier or other party)s, e.g. method=confirm or process with params.ids. describe_model (model_schemas.get) lists a model's methods and their parameters. Required: method.
list_all_fulfil_customer_shipment_counts
Count customer shipments matching an optional where filter. The count is in result.
list_all_fulfil_customer_shipments
List customer shipments with Fulfil's find method: filter with where, pick fields, sort with ordering. The connector follows the cursor through every page.
get_single_fulfil_customer_shipment_by_id
Get one customer shipment by id (Fulfil's serialize: the server's summary of the record). For specific fields use list with where {"id":
create_a_fulfil_customer_shipment
Create one or more customer shipments in a single call. Send the records as params.vlist (an array, even for one record); nested lines are allowed. Returns the new ids. Required: params.
update_a_fulfil_customer_shipment_by_id
Update data fields of one customer shipment. Send the new values as values; change state with execute (a workflow method such as confirm or process), never by writing the state field. Required: id, values.
fulfil_customer_shipments_bulk_update
Write the same values to several customer shipments in one call: send params.ids and params.values. Required: params.
delete_a_fulfil_customer_shipment_by_id
Permanently delete one customer shipment. Required: id.
fulfil_customer_shipments_execute
Call a workflow or other model method on customer shipments, e.g. method=confirm or process with params.ids. describe_model (model_schemas.get) lists a model's methods and their parameters. Required: method.
list_all_fulfil_me
The user this API key acts as, with its scopes (system.whoami). The connector calls it to check the key when an account connects.
get_single_fulfil_model_schema_by_id
Describe one model: its fields, types, allowed values and methods with their parameters. The id is the model name, e.g. sales_order. Required: id.
list_all_fulfil_models
List the Fulfil models this API key can reach (v3 names such as sales_order). Use the names as model in the records methods.
list_all_fulfil_product_counts
Count products matching an optional where filter. The count is in result.
list_all_fulfil_products
List products with Fulfil's find method: filter with where, pick fields, sort with ordering. The connector follows the cursor through every page.
get_single_fulfil_product_by_id
Get one product by id (Fulfil's serialize: the server's summary of the record). For specific fields use list with where {"id":
create_a_fulfil_product
Create one or more products in a single call. Send the records as params.vlist (an array, even for one record); nested lines are allowed. Returns the new ids. Required: params.
update_a_fulfil_product_by_id
Update data fields of one product. Send the new values as values; change state with execute (a workflow method such as confirm or process), never by writing the state field. Required: id, values.
fulfil_products_bulk_update
Write the same values to several products in one call: send params.ids and params.values. Required: params.
delete_a_fulfil_product_by_id
Permanently delete one product. Required: id.
fulfil_products_execute
Call a workflow or other model method on products, e.g. method=confirm or process with params.ids. describe_model (model_schemas.get) lists a model's methods and their parameters. Required: method.
list_all_fulfil_purchase_order_counts
Count purchase orders matching an optional where filter. The count is in result.
list_all_fulfil_purchase_orders
List purchase orders with Fulfil's find method: filter with where, pick fields, sort with ordering. The connector follows the cursor through every page.
get_single_fulfil_purchase_order_by_id
Get one purchase order by id (Fulfil's serialize: the server's summary of the record). For specific fields use list with where {"id":
create_a_fulfil_purchase_order
Create one or more purchase orders in a single call. Send the records as params.vlist (an array, even for one record); nested lines are allowed. Returns the new ids. Required: params.
update_a_fulfil_purchase_order_by_id
Update data fields of one purchase order. Send the new values as values; change state with execute (a workflow method such as confirm or process), never by writing the state field. Required: id, values.
fulfil_purchase_orders_bulk_update
Write the same values to several purchase orders in one call: send params.ids and params.values. Required: params.
delete_a_fulfil_purchase_order_by_id
Permanently delete one purchase order. Required: id.
fulfil_purchase_orders_execute
Call a workflow or other model method on purchase orders, e.g. method=confirm or process with params.ids. describe_model (model_schemas.get) lists a model's methods and their parameters. Required: method.
list_all_fulfil_record_counts
Count records of the given model matching an optional where filter. The count is in result. Required: model.
list_all_fulfil_records
List records of the given model with Fulfil's find method: filter with where, pick fields, sort with ordering. The connector follows the cursor through every page. Required: model.
get_single_fulfil_record_by_id
Get one record by id (Fulfil's serialize: the server's summary of the record). For specific fields use list with where {"id":
create_a_fulfil_record
Create one or more records of the given model in a single call. Send the records as params.vlist (an array, even for one record); nested lines are allowed. Returns the new ids. Required: model, params.
update_a_fulfil_record_by_id
Update data fields of one record. Send the new values as values; change state with execute (a workflow method such as confirm or process), never by writing the state field. Required: id, model, values.
fulfil_records_bulk_update
Write the same values to several records of the given model in one call: send params.ids and params.values. Required: model, params.
delete_a_fulfil_record_by_id
Permanently delete one record. Required: id, model.
fulfil_records_execute
Call a workflow or other model method on records of the given model, e.g. method=confirm or process with params.ids. describe_model (model_schemas.get) lists a model's methods and their parameters. Required: model, method.
get_single_fulfil_report_schema_by_id
Describe one report's parameters. The id is the report name. Required: id.
list_all_fulfil_reports
List the reports available in the workspace.
fulfil_reports_execute
Run a report: report is its name (from reports.list), params its parameters (report_schemas.get lists them). Required: report.
list_all_fulfil_sales_order_counts
Count sales orders matching an optional where filter. The count is in result.
list_all_fulfil_sales_orders
List sales orders with Fulfil's find method: filter with where, pick fields, sort with ordering. The connector follows the cursor through every page.
get_single_fulfil_sales_order_by_id
Get one sales order by id (Fulfil's serialize: the server's summary of the record). For specific fields use list with where {"id":
create_a_fulfil_sales_order
Create one or more sales orders in a single call. Send the records as params.vlist (an array, even for one record); nested lines are allowed. Returns the new ids. Required: params.
update_a_fulfil_sales_order_by_id
Update data fields of one sales order. Send the new values as values; change state with execute (a workflow method such as confirm or process), never by writing the state field. Required: id, values.
fulfil_sales_orders_bulk_update
Write the same values to several sales orders in one call: send params.ids and params.values. Required: params.
delete_a_fulfil_sales_order_by_id
Permanently delete one sales order. Required: id.
fulfil_sales_orders_execute
Call a workflow or other model method on sales orders, e.g. method=confirm or process with params.ids. describe_model (model_schemas.get) lists a model's methods and their parameters. Required: method.
Why Truto
Why use Truto’s MCP server for Fulfil
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1050+ integrations.
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.
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.
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.
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.
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.
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 Fulfil in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.
Link your customer’s Fulfil account
Use Truto’s frontend SDK to connect your customer’s Fulfil account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
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.
Call our API, we call Fulfil
Truto’s Proxy API is a 1-to-1 mapping of the Fulfil API. You call us, we call Fulfil, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Fulfil’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Fulfil on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
How does authentication work for Fulfil accounts connected through Truto?
Your end users connect their Fulfil account once through Truto's connect flow, and Truto manages credential storage, refresh, and secure proxying of every API call. You never handle Fulfil API keys directly in your application.
How do we change the state of a sales order or shipment without breaking Fulfil's accounting?
Never patch state fields directly. Use the `fulfil_sales_orders_execute` or `fulfil_customer_shipments_execute` tools to invoke workflow methods like `confirm` or `process`. This ensures Fulfil generates the correct journal entries and stock movements.
Can we handle merchants with heavily customized Fulfil instances?
Yes. Use `get_single_fulfil_model_schema_by_id` and `list_all_fulfil_models` to introspect each merchant's custom fields and allowed values at runtime, then shape your writes accordingly rather than hardcoding a schema.
What about rate limits during peak events like Black Friday?
Fulfil's API is built for high-volume commerce with rate limits in the thousands of requests per minute. Truto additionally handles retries, backoff, and queuing so your integration stays stable during traffic spikes.
How do we efficiently poll for new or changed records?
Each core resource (sales orders, customer shipments, products, purchase orders, contacts) exposes a count endpoint alongside the list endpoint, so you can cheaply detect changes before paginating. You can also use the generic records endpoints for broader queries across Fulfil models.
Can we run bulk operations instead of one-by-one writes?
Yes — contacts, products, sales orders, purchase orders, and customer shipments all support bulk update operations, which is critical when syncing large catalogs or reconciling batches of orders from external systems.
From the Blog
Fulfil integration guides
Deep dives, architecture guides, and practical tutorials for building Fulfil integrations.
Fulfil
Get Fulfil integrated into your app
Our team understands what it takes to make a Fulfil integration successful. A short, crisp 30 minute call with folks who understand the problem.