Ask the lead for the missing waivers or heights — one email

POST

/bookings/{booking_id}/readiness-requests

curl --request POST \
  --url https://quikstik-core.fly.dev/bookings/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/readiness-requests \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'x-tenant-id: 2489E9AD-2EE2-8E00-8EC9-32D5F69181C0' \
  --data '{ "kind": "waiver", "participant_ids": [ "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" ] }'

• Production

Mints the existing readiness links (/w/{token}) for the participants still missing the thing (participant_ids narrows it) and sends ONE message to the lead through the hub’s mouth: the content gate runs and info@ is in copy (a single-recipient guest email). Idempotent per (booking, kind, UTC day): a repeat is 200 {replayed: true, links: []} (tokens are stored hashed, so a repeat cannot show them again) and sends nothing. 409 nothing_missing, 422 no_lead_email.

Authorizations

• bearerAuth
• operatorKey

Parameters

Path Parameters

booking_id

required

string format: uuid

Header Parameters

x-tenant-id

required

string format: uuid

Tenant identifier (UUID).

Authn/authz semantics are intentionally TBD for this contract slice; this header exists to keep the contract explicitly multi-tenant from day 0.

Request Body^required

Media typeapplication/json

object

kind

required

string

Allowed values: waiver heights

participant_ids

Array<string>

Responses

200

Sent (or replayed).

Media typeapplication/json

object

kind

required

string

message_id

required

string format: uuid

status

string

replayed

required

boolean

links

required

Array<object>

object

participant_id

required

string format: uuid

url

required

string

Example ^generated

{
  "kind": "example",
  "message_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
  "status": "example",
  "replayed": true,
  "links": [
    {
      "participant_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
      "url": "example"
    }
  ]
}

401

Missing or invalid session bearer token

Media typeapplication/json

object

reason

required

Stable, machine-readable reason code (e.g. “sold_out”, “processor_not_configured”, “rail_refused”).

string

Example

{
  "reason": "sold_out"
}

403

The session’s effect authority does not cover this operation

Media typeapplication/json

object

reason

required

Stable, machine-readable reason code (e.g. “sold_out”, “processor_not_configured”, “rail_refused”).

string

Example

{
  "reason": "sold_out"
}

404

No such booking or participant_not_on_booking.

409

nothing_missing, bad_transition.

422

bad_kind, no_lead_email, or a content-gate refusal.

503

No durable backend is wired for this operation (fail-closed)

Media typeapplication/json

object

reason

required

Stable, machine-readable reason code (e.g. “sold_out”, “processor_not_configured”, “rail_refused”).

string

Example

{
  "reason": "sold_out"
}