Upload a level photo
/api/levels/{id}/imageA line-for-line mirror of POST /api/services/{id}/image, stored in level-photos (migration 0110) instead. Not admin-gated, and not re-gated by planAllows('floors') either: that check belongs to CREATING a level; one that already exists already cleared it, same as PATCH/DELETE on this row.
Authorization
sessionCookie The dashboard's Supabase Auth session cookie, set at sign-in. Large sessions are split across
numbered chunks (…auth-token.0, .1), so treat this as a cookie family rather than one name.
Every request re-validates it against the Auth server (getUser()), never by decoding the cookie
locally: a JWT nothing has checked is not a credential. Tenancy is then read from the verified
app_metadata.company_id claim and enforced by row-level security; it is never read from request
input, on any route, ever.
role (admin / staff) is deliberately not in RLS. It gates specific actions in route code,
the operations marked admin below, so hiding a button in the UI is cosmetic only, and a route's
own check is the enforcement.
In: cookie
Path Parameters
Level id.
Request Body
multipart/form-data
The level photo. Sent as multipart/form-data under the field name file.
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/levels/string/image" \ -F file="string"{ "ok": true, "imageUrl": "http://example.com"}Delete a level (admin) DELETE
Unlike a table, this never 409s: `book_areas.level_id` and `book_tables.level_id` are both ON DELETE SET NULL (migration 0030), so deleting a level always succeeds and simply ungroups whatever areas or tables sat directly on it.
Remove a level photo DELETE
Deletes the stored object and nulls `image_url`. Storage removal is best-effort and its failure does not fail the request.