Launch checklist

Production credentials are issued after this checklist is complete. It is not paperwork — it is the list of things that, when missing, generate support calls at the worst possible hour.

Checklist

Authentication

• [ ] Token is cached and reused, not requested per call
• [ ] Token is renewed before expiry, not after a 401
• [ ] TOKEN_EXPIRED and INVALID_CREDENTIALS are handled differently
• [ ] The secret lives on your server — not in a mobile app or browser bundle

Stores

• [ ] A store can be registered and later updated through the same PUT
• [ ] availableFleets is shown to the restaurant in a usable way
• [ ] A fleet can be attached and changed
• [ ] 409 ALREADY_HIZLIYO_PARTNER shows a sensible message, not a raw error

Orders

• [ ] X-Idempotency-Key is sent and stable per order
• [ ] readyAt reflects when the food actually leaves the kitchen
• [ ] Dropoff coordinates come from a real geocode, not a district centroid
• [ ] At least three error codes are handled distinctly — suggested: FLEET_UNAVAILABLE, FLEET_SUSPENDED, COORDINATE_MISMATCH
• [ ] A failed order is not retried blindly in a loop

Webhooks

• [ ] Endpoint is reachable over HTTPS and returns 2xx quickly
• [ ] Signature is verified against the raw body
• [ ] A tampered body is rejected — you tested this
• [ ] Unknown event types are ignored without failing
• [ ] Events are deduplicated on eventId
• [ ] Out-of-order events do not move a delivery backwards

Cancellation

• [ ] Cancel is possible before pickup
• [ ] The control disappears at PickedUp
• [ ] CANCEL_TOO_LATE is handled gracefully

Operations

• [ ] You can find a delivery by your own order id when a restaurant calls
• [ ] The status timeline is visible to your support staff
• [ ] Someone owns first-line support for restaurants — that is you, not us

Requesting production access

Send us:

1. Your sandbox client id
2. The webhook URL for production
3. A rough volume estimate — restaurants, orders per hour, peak windows
4. A technical contact and a commercial contact

We check the sandbox activity against the checklist and issue hzl_live_ credentials.

First week in production

• Start with a handful of restaurants, not the whole estate
• Watch your error rates by code; a rising COORDINATE_MISMATCH usually means an address mapping problem on your side
• Keep the sandbox credentials — every future change should be tested there first

We are watching too

We monitor error patterns per integrator. If we see something climbing, we will contact you before it becomes a restaurant complaint.