Adjust a variant's stock
/api/products/{id}/variants/{variantId}/stockSame three reasons and two shapes POST /api/products/{id}/stock takes, calling book_product_variant_stock_adjust() (migration 20260918100000) against the variant's own stock_on_hand instead of the parent product's. Appointments only, see POST /api/products.
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
Product id (routing only, not consulted by the RPC).
book_product_variants id.
Request Body
application/json
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/variants/string/stock" \ -H "Content-Type: application/json" \ -d '{ "reason": "received" }'{ "stockOnHand": 0}A variant's recent stock movements GET
Same shape GET /api/products/{id}/stock takes, off the separate book_product_variant_stock_movements ledger (migration 20260918100000): a variant's stock history is independent of its parent product's (frozen, unused) own stock_on_hand. **Appointments only**, see POST /api/products.
Create a product category POST
A named shelf products hang off on the Products list ("Hair care", "Tools"), purely for finding things; it never changes a price (migration 0176). New categories land at the end of the shelf (`sort_order = max+1`). v1 is flat, name-only: no rename or reorder route exists yet. **Appointments only**, see POST /api/products.