Shared

Add a tier (admin, or deposit_staff_editable)

post/api/organization/no-show-fee-tiers

Same gate PATCH /api/companies already applies to noShowFeeType/noShowFeeAmountCents/noShowFeePercentage: admin, or a staff member once this org's admin has turned on depositStaffEditable (migration 0075). A tier is part of the same money-policy surface those three columns are, not an ordinary tenant setting.

Capped at 6 tiers per company (a soft, also server-checked ceiling: same "data-entry accident, not a business" reasoning book_special_hours' own 6-window cap gives). thresholdHours must be unique per company (book_no_show_fee_tiers_one_per_threshold); a duplicate is a 409.

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

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/organization/no-show-fee-tiers" \  -H "Content-Type: application/json" \  -d '{    "thresholdHours": 0,    "feeType": "fixed"  }'
{  "ok": true,  "tier": {    "id": "string",    "threshold_hours": 0,    "fee_type": "fixed",    "fee_amount_cents": 0,    "fee_percentage": 0  }}