Get the preparation time
Returns the current preparation time: base time plus rush, already added up. This is the number to show as “ready in about X min” on the menu and in checkout, and exactly what POST /orders uses to set estimatedReadyAt on an as-soon-as-possible order.
It is a separate endpoint because /restaurant and /menu are cached at the edge for up to 5–11 minutes, and rush is exactly when that delay hurts. This response is never cached (no-store). Cache it yourself for 20–30 seconds, and fetch it again when checkout opens.
Same authentication as the rest of the API (API key or trusted browser origin), so you can call it from the browser on a verified domain. Rate limit: 600 requests per 60 seconds per slug and IP.
Authentication
Either this or a trusted browser origin. The restaurant’s API key, sent as Authorization: Bearer lbs_…. Use it from your server only, never in browser code. Keys are issued per restaurant by LettBestilt.
Either this or an API key. No key is needed when the request’s Origin header is trusted for this restaurant: https://{slug}.lettbestilt.no, a verified domain of the restaurant, or a partner origin LettBestilt has bound to the restaurant. Browsers set Origin themselves; it is not something you configure. Not accepted by GET /site-gate, which requires an API key.
Query parameters
Response
The current preparation time, already added up: base time plus rush. Show pickupMinutes or deliveryMinutes as “about X min”. They are exactly what POST /orders uses to set estimatedReadyAt (now plus the minutes) on an as-soon-as-possible order. rushDelayMinutes above 0 means the kitchen has turned on rush, which turns itself off at the next midnight (Oslo time). Do not calculate anything yourself; show the numbers as they are.