Merchable API. Orders, from your own systems.
A small, versioned REST API for placing and tracking account orders from your ERP, procurement tool or internal app — with prices, stock and webhooks built in.
One base URL. One key.
Plain JSON over HTTPS. Create an API key under Settings → Developer, send it as a bearer token, and you are in.
- Scoped keys. Grant only what the integration needs — read designs, place orders.
- Idempotent ordering. Retry safely — the same key never places the same order twice.
- OAuth for apps. Building for many Merchable accounts? The same OAuth 2.1 tokens as MCP work here.
- Base URL
- https://api.merchable.co/v1
- Format
- JSON · OpenAPI 3.1
- Auth
- Bearer mchp_… · OAuth 2.1
- Reference
- api.merchable.co/docs
Everything an order needs, nothing it doesn't.
Designs
Every variant with its unit price and live stock status, in one read.
Shops
Your shops, the designs in them and their collections.
Orders
Quote, place, cancel and track — shipments, tracking and a full event log.
Webhooks
Set a URL on the order and get every status change, signed, with retries.
Your first order in three calls.
- Read a design to get the variant ids, prices and stock you need.
- Quote it to see the full total, shipping and tax, without committing.
- Place it with an idempotency key, and let the webhook tell you when it ships.
curl https://api.merchable.co/v1/orders \
-H "Authorization: Bearer mchp_your_key" \
-H "Idempotency-Key: po-2026-0042" \
-H "Content-Type: application/json" \
-d '{
"external_reference": "PO-2026-0042",
"items": [
{ "design_id": "d8Xk2mQz", "colour": "Black", "size": "L", "quantity": 12 }
],
"delivery": {
"type": "delivery",
"address": { "line1": "1 Example St", "city": "Melbourne",
"state": "VIC", "postcode": "3000", "country": "AU" }
},
"webhook_url": "https://example.com/merchable/orders"
}'
Merch that fits your workflow.
Order from the tools your team already uses, and let Merchable handle the rest.