Add up to 50 products in one call
Partner key + restaurant key. For large menus and LettBestilt MCP. products is 1–50 products, each with its own categoryId and the same fields as POST …/categories/{categoryId}/products. All or nothing in one transaction: one invalid product and none are created. A category that is not the restaurant’s gives 422 with the path products.N.categoryId, not 404. The products are placed last in their category in the order they are sent, and the response has them in the same order. The whole batch counts against the product limit. A price above 0 and below 500 øre (5 kr) is saved, but gives a warning in warnings ([{ path, message }]): it looks like kroner (149 for 149 kr). Paths look like products.2.basePrice. Names and descriptions are trimmed and cleaned (links, email addresses, HTML, javascript: and invisible direction marks are removed); the count is in textCleaned, and a name that ends up empty gives 422. GET /api/v1/menu is CDN-cached (s-maxage=30, stale-while-revalidate=300, at most 330 seconds), so the website can show the old menu for up to six minutes; the response has notice about it.
Authentication
The partner key (lbp_test_… or lbp_live_…), sent as Authorization: Bearer lbp_… and created in LettBestilt Partner under Partner key. It belongs to the whole 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, and the key must never be in a browser. A TEST key sees and creates only sandboxes; LIVE keys work once LettBestilt Partner is open. A suspended or archived partner, a revoked key and a restaurant key (lbs_…) here give 401 UNAUTHORIZED; an expired key gives 401 KEY_EXPIRED.
The restaurant’s own key (lbs_test_… or lbs_live_…) for calls about one restaurant in the partner API, sent together with the partner key. 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. A restaurant 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
The restaurant’s slug. It must match the restaurant key in X-LettBestilt-Restaurant-Key.