Question 1

What does the API cover?

Accepted Answer

The REST API reaches orders, shipments, rates, labels, address validation, tracking, invoices, agents, and account management. Carrier tracking events arrive in the same shape whichever carrier produced the scan. Authentication uses API keys scoped to your account or sub-accounts, and you create, rotate, scope, and track those keys yourself. The developer portal carries the API documentation, an API explorer, and developer onboarding, and pre-built connectors cover 300+ integrations before you write any custom code.

Question 2

Which systems can I connect?

Accepted Answer

The connector framework reaches 300+ integrations, including 154 WMS, 3PL, OMS, and IMS platforms such as ShipBob, ShipMonk, Extensiv, and ShipHero. Trading partners run over EDI X12 with the 204, 210, 214, and 856 transaction sets and partner management built in. When a system is not in the catalog, the framework generates a connector with AI. Device data arrives through that framework too, with a registry for sensors, RFID, and GPS from Samsara, Tive, and Zebra.

Question 3

How do I move data in and out?

Accepted Answer

Import and export CSV files, and let AI-assisted mapping match the columns for you with a mix of LLM, fuzzy, and synonym matching. For everything that runs on a schedule or a trigger, build it on the visual workflow builder, which reaches 1,868+ workflow integrations across ERPs, CRMs, stores, databases, and AI tools.

Question 4

How does MCP work?

Accepted Answer

MCP (Model Context Protocol) lets the AI tools your team already runs connect directly to CommerceShip data and actions. Implement the protocol once and any MCP-capable model works, so there is no integration to write per model. Each request authenticates with an API key. To move data the other way, out of an ERP, a warehouse system, or a data warehouse, use the integration catalog and workflow automation.

Question 5

Can I build custom agents?

Accepted Answer

Yes. Draft an agent with specific tools (rate shopping, label generation, invoice auditing), knowledge sources (your SOPs, carrier contracts, business rules), and a graduated autonomy level on a six-level scale from Manual (0) to Autonomous (5). Simulate it against your own data, set the thresholds and the kill switch, then publish it. Each agent operates within the boundaries you set, and every decision it makes is logged on a reviewable timeline.

Question 6

What webhook events are available?

Accepted Answer

Webhooks cover 27+ events across 7 domains, including tracking updates, order status changes, label generation, agent actions, invoice processing, and exception alerts. You configure which events to subscribe to and where to send them. Every payload carries an HMAC signature so your endpoint can verify it came from CommerceShip.

Fit CommerceShip into your existing stack

Systems integration on CommerceShip

How your systems connect to CommerceShip

Post orders from your system and read tracking back

Build a handoff in the workflow builder

Read normalized data, whichever system sent it

Send us your system list for a demo

Systems Integration FAQs