Create or replace an intake form (admin)

One form per target, where the target is either a single service or the whole org. serviceId: null means "every booking in this org", which is also what a table-reservations org always uses; it has no services. Two partial unique indexes in migration 0024 make that unambiguous, and this route upserts against them by reading first: PostgREST's onConflict emits a bare ON CONFLICT (company_id, service_id), which Postgres cannot infer against an index carrying a WHERE clause.

Written with the caller's own RLS-scoped client, NOT service-role. Unlike book_notification_templates, 0024 gives book_intake_forms a plain tenant policy, so RLS plus the JWT company_id claim already is the boundary. The composite foreign key means a serviceId belonging to another org is refused by the database rather than by route code, and surfaces as a 400.

There is no DELETE, deliberately. book_intake_responses references the form on delete cascade, so dropping a form would take every answer any guest ever gave with it, and a submitted intake is a record. active: false is the retire switch and it is part of this body.

Shared by both engines and therefore NOT vertical-guarded: a form asks a guest questions, which is plumbing like customers and notifications, not booking logic.

Response BodyCopy Anchor Link

curl -X PUT "https://example.com/api/intake" \  -H "Content-Type: application/json" \  -d '{    "title": "string",    "fields": [      {        "label": "string",        "type": "text"      }    ]  }'

{  "ok": true,  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08"}