Booking API course · updated 2026-10-05
Lesson 14: go-live checklist and what to tell the office
The last mile: what to verify before pointing real customers at your screens, what the office will see, and how to support the first orders.
Before you start
- Lessons 1 to 13
- ## Before the first customer
- GET /company shows is_online true and payments_ready true. 2. GET /sizes returns every size the office expects, with the right prices. 3. Closed days from GET /availability match the office calendar. 4. POST /check refuses an out-of-area ZIP and accepts an in-area one. 5. A 10 dollar real order goes through /intents, the card and /confirm, shows on the dispatch board and is refunded from Order History. 6. Conversion tags fire after /confirm. 7. The rental agreement is shown and the checkbox is required. 8. Your domain is in Allowed domains; staging domains too if used. 9. The server key, if any, is not in client code.
- ## What the office sees
The order appears on the dispatch board already paid, with channel api on the order; the customer appears in Customers; the invoice is created; the office gets email, SMS, push and the in-app alert with sound. Held orders appear in the review queue. Nothing else changes for the office: your screens are just another door. - ## Support and monitoring
Log session_id, payment_intent_id and order_number on your side for every attempt. Watch 409 codes: a spike of out_of_service_area or date_closed means the office changed settings and your cached data is stale. Watch 429: you are calling /quote too often; debounce the inputs. Watch upstream (502): retry POST /confirm with the same pair after a few seconds and read GET /sessions to see the state. - ## Where to ask
support@dumpstercontrols.io for the API, the office of the company for prices and rules, and Tresha inside the app for anything in this manual. - ## Materials
If GET /materials says enabled: your screens ask the material before the size, show the explanation and the confirmation when requires_ack is true, send material to /quote and /intents, and handle 409 material_not_allowed by offering details.allowed_sizes. Compare one quote per material against the office's price list.
What happens next
- Done. From here the engine keeps improving behind your screens: every fix we ship to the hosted page reaches your integration with no change on your side.
Troubleshooting
A customer says the card was charged but sees no order number.
The /confirm call did not reach us (page closed, network). The card was authorized, not charged: Nobody is charged without an order: the authorization is only captured when the order is created, and an authorization that never becomes an order is released or expires on its own. Within about 15 minutes of an authorized card without an order, the customer and the company are told by email and SMS so the office can finish it by hand. Look the session up with GET /sessions/:id, and if the authorization is still valid call POST /confirm again with the same session_id and payment_intent_id.
Related guides
- Lesson 1: what the Booking API is and how the pieces fit
- How to use the Booking API for your own booking screens in Dumpster Controls
© 2026 Dumpster Controls. All rights reserved. Made in the USA.