Sandbox and go-live
Sandbox
Section titled “Sandbox”A sandbox is a separate test company in Orda with its own key. Its data never mixes with production — company isolation is enforced by the database. Create, change and cancel orders, build and approve routes, test webhooks as much as you need.
Ask your Orda manager (contacts on the website) with the company name and the e-mail of your technical contact. You get a test company code, an administrator login and an API key.
Tip: keep two connection profiles in your system — “Test” and “Production” (host, key, webhook secret).
What to test
Section titled “What to test”- The key works:
GET /orders→200. - Directories load, and re-sending updates instead of duplicating.
- Orders: a batch of 100–1000 rows; re-sending gives
updated. - Row errors (
result: "error") reach your exchange log with their codes. - Retrying with the same
Idempotency-Keycreates nothing twice. - Webhooks:
POST /webhooks/{id}/testarrives, the signature verifies, you answer2xxwithin 10 s. - Cancelling in your system →
status: "cancelled"in Orda. - Routes: a plan is built and approved; your system receives
plan.approved.
Go-live checklist
Section titled “Go-live checklist”- Production key issued from a service account and stored in a secret store.
- The key has only the scopes it needs.
- The webhook URL is https with a valid certificate, reachable from the internet.
- Webhook signatures are verified; timestamps older than 5 minutes are rejected.
- Retries on
429/5xxwith back-off;Idempotency-Keyon every write. - Exchange log on your side: what was sent, what came back, which rows failed.
- A responsible person on your side and an Orda support contact.