List this company's tiered no-show fees
/api/organization/no-show-fee-tiersEvery row of book_no_show_fee_tiers (migration 0137) this company has configured, in threshold_hours order: what DepositsCard's tier editor renders and what GET /api/payments/no-show-fee resolves a suggestion from. Readable by any member; only the writes below are gated.
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
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/api/organization/no-show-fee-tiers"{ "tiers": [ { "id": "string", "threshold_hours": 0, "fee_type": "fixed", "fee_amount_cents": 0, "fee_percentage": 0 } ]}Return a date to the recurring week (admin, or manage_org_settings) DELETE
Removes the row, so the date follows the ordinary weekly hours again. **Emphatically not the same as saving it with no windows**, which is how a business says it is shut. Deleting a date that was never set is not an error: the caller asked for this date to follow the ordinary week, and it now does.
Add a tier (admin, or deposit_staff_editable) POST
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.