Sandbox and test orders
Your sandbox is ready as soon as you sign up: a sandbox key, a test restaurant with a real looking menu, test orders on demand and a request log that tells you why a call failed.
#Sandbox keys
Your key ID looks like lpk_8f2c41a9e07b5d13c6a2f904 and your secret like lps_.... A sandbox key uses the same base URL and the same endpoints as a live one, but it can only link Laayo test stores, so nothing you do reaches a real customer. GET /v1/partner/me shows "sandbox": true.
The secret is shown once when you sign up. Rotate it in the console or with POST /v1/partner/secret/rotate; the old one keeps working for 24 hours.
#Your test restaurant
Every sandbox gets Laayo Test Kitchen in Birtamod, not visible to customers. It behaves like a real store: it opens, closes, goes busy, and takes orders.
#Link it
The keys page shows a link code for the test kitchen, for example 731 058. Send it with POST /v1/stores/link exactly as you would with a real owner. When it expires, the console shows a fresh one.
#Test orders
Press Send test order on the Go-live page in the console. The order arrives as order.created, by webhook or polling, like a real one. Then take it through accept, preparing and ready with POST /v1/orders/{id}/accept, POST /v1/orders/{id}/preparing and POST /v1/orders/{id}/ready.
Map the test kitchen's items first, so the order carries your item IDs. See Item mapping.
#The request log
The console keeps every call you make with its status, the signature check result and the reason for any refusal. Start there when something fails. Bodies are kept 7 days, with phone numbers masked.
#What the sandbox cannot do
- Sandbox keys cannot link real restaurants. That returns 403 sandbox_live_store.
- There are no sandbox endpoints in the API. Test orders and fresh test link codes come from the console.
- No payouts are made for test orders.