Appointments engine

Upload a product image

post/api/products/{id}/image

Stores the file at {companyId}/{productId} in the product-images bucket and writes a cache-busted public URL onto the product row. Not gated on manage_services: a photo is part of editing the product, same posture as the equivalent service-image route. Ownership is checked BEFORE the upload, so a request naming a product the caller does not own is a 404 with nothing written. Appointments only, see POST /api/products.

Authorization

sessionCookie
sb-qxrvgfkjyvbngipqvslu-auth-token<token>

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

id*string

Product id.

Request Body

multipart/form-data

The product image. 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/products/string/image" \  -F file="string"
{  "ok": true,  "imageUrl": "http://example.com"}