not a side door
The same actions,the same limits, the same record.
Your systems will read conversations and orders, send replies through our pipeline, and hear about every change through signed webhooks.
the problem today
Five entrances, five bugs.Unless they share one path.
Support tools often bolt on an API that skips the rules the panel follows.
Then a script can do what no agent may, and nobody can say who did it.
So every call will go through the same path as everything else.
how it will work
Four parts.
- 1API keysCreate, scope and revoke. There's no rotate button: you rotate by creating a new key and revoking the old one.
- 2ReadConversations, orders and cases, from the same source the panel uses.
- 3WriteSend replies through our pipeline. When case actions arrive, your key gets its own ceiling like any other actor, and the same duplicate guard and record.
- 4Signed webhooksA small set of event types, retried with backoff, and a delivery log where failures are visible and you can retry by hand.
- Agent in the panel
- Fin
- A workflow
- A macro
- Your API key
fair is fair
If something goes wrong.
- If your endpoint is down, we retry with backoff and the delivery log shows it.
- A failed delivery is shown as failed, not as if it never happened.
boundaries, on purpose
What this does not do.
No way around your limits
An API key is an actor like any other, with its own ceiling.
No bulk endpoint
One call, one decision, one record.
short answers
Questions from engineers.
Scale and Enterprise. Enterprise adds higher rate limits. Pricing →
It will live at docs.commercereply.com. Event names and payloads go there once they're final, not on this page.
An agent approves a cancellation, we send a signed webhook, your warehouse stops the shipment. If your endpoint is down, we retry.
goes well with
Related.
Plug in your systems,without a side door.
Messages work today. The API and webhooks are later on the roadmap, and the shops that join now get a say in the order.