CommerceShip Logo
Log inGet access

Build on the CommerceShip API

REST endpoints for each module, signed webhooks, and an MCP server for AI tools. An API key authenticates all three.

Read the API docsGet API access
Data Normalization
Carrier responses
FedEx
ActualDeliveryDate
UPS
deliveryDate
USPS
delivery_timestamp
Normalized
Standard response
"delivered_at"
"status"
"carrier"
ResultYour code handles one format, regardless of carrier

Developer resources

API reference

Endpoints, authentication, and request examples.

Open the API reference
Webhooks

Signed events for orders, shipments, and invoices. Verify a payload with its HMAC signature.

Read about webhooks
MCP and A2A

AI tools connect over MCP with an API key. External agents read the agent card and call the live skills over JSON-RPC.

Read about MCP
Changelog

Releases by month, with an RSS feed and a JSON feed.

See what changed

Which one to use

Use the REST API when your own system creates orders, requests rates, or generates labels. Add webhooks when that system needs to hear about a status change as it happens. Use the MCP server when a person works in an AI tool and needs CommerceShip data there.

API keys can be scoped, rotated, and tracked by usage. To see how engineering teams use the platform, read the engineering page.