Ask LettBestilt for go-live approval
Partner key + restaurant key. Asks LettBestilt to check a real restaurant before it goes live for the first time: menu, opening hours, payment, agreements, company details, website, domain, API key, owner and allergens. The onboarding steps must be ready (goLive.readyToRequest in GET …/{slug}), otherwise 422 GO_LIVE_NOT_READY with details.missing. The checklist runs first: an error gives 422 GO_LIVE_CHECKS_FAILED with details.checks and nothing is stored; warnings do not block. An approval is valid for 30 days and never sets the restaurant live: the owner does that.
Real restaurants only, so it needs a live partner key (available once LettBestilt Partner is open). A sandbox gives 409 SANDBOX_NOT_SUPPORTED. At most 15 requests per hour per restaurant and 30 per partner (shared with the partner portal).
Authentication
The partner key, sent as Authorization: Bearer lbp_test_…. Created in LettBestilt Partner under Partner key. It belongs to the partner, not to a restaurant, and only works against /api/v1/partner. Server to server only: a request with an Origin header is rejected with 403 FORBIDDEN. A test key sees and creates only sandboxes; live partner keys are not available yet. A revoked key, a restaurant key (lbs_…) here, or a suspended or archived partner returns 401 UNAUTHORIZED; an expired key returns 401 KEY_EXPIRED.
The restaurant’s own key (lbs_test_… or lbs_live_…), sent in X-LettBestilt-Restaurant-Key together with the partner key for calls about one restaurant. The key must have full access (scope *, otherwise 403 INSUFFICIENT_SCOPE), belong to a restaurant the partner owns, and be in the same environment as the partner key (otherwise 401 UNAUTHORIZED). A slug that does not exist, belongs to another partner or does not match the key always gives the same 404 RESTAURANT_NOT_FOUND. Older keys without an environment in the prefix (lbs_<random>) are not accepted here; rotate them in LettBestilt Partner.
Path parameters
Response
En sendt go-live-forespørsel.