Webhooks

Delieta does not call your server when an order changes status. There is no webhook path in the published OpenAPI. That is not a docs omission — the operation does not exist.

What to do instead of listening

After POST /api/v1/orders you may get pending_acceptance. The ticket leaves that state when someone in the kitchen accepts or rejects, or when the time limit passes. None of those events is caused by your backend, so the only legal read is GET /api/v1/orders/{id}.

Polling spends the read budget. It does not spend the budget for creating another order.

404 not_found on that GET means “there is no such order for this key”. Another company’s order answers the same way — this is not an oracle.

What is not here

There is no signed POST to https://your-shop/hooks/orders. There is no partner webhook secret. There are no exponential retries on our side.

Your company’s payment for Delieta goes through Stripe and is a panel matter, not Partner API. Do not mix it with the kitchen ticket’s life cycle.

When partner webhooks exist, they will appear as a new operation in GET /api/v1/openapi and on the Partner API page. Until then OpenAPI is the list of what exists.