Skip to content

Re-resolve one booking's policy snapshot, with a reason

POST
/bookings/{booking_id}/policy/re-resolve
curl --request POST \
--url https://quikstik-core.fly.dev/bookings/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/policy/re-resolve \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'x-tenant-id: 2489E9AD-2EE2-8E00-8EC9-32D5F69181C0' \
--data '{ "reason": "example" }'

The explicit, never-implicit way a booking is moved onto the merchant’s CURRENT terms: resolves the booking’s policy now, appends it as the booking’s next snapshot, and appends a PolicyReResolvedV1 amendment (with the reason) to its agreement chain, in one transaction. Session-bearer only (a human). 404 booking_not_found / no_agreement; 409 booking_cancelled; 422 reason_required (empty, or over 500 characters).

booking_id
required
string format: uuid
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.

Media typeapplication/json
object
reason
required
string
>= 1 characters <= 500 characters

Example generated

{
"reason": "example"
}

Re-resolved

Media typeapplication/json
object
booking_id
required
string format: uuid
snapshot_seq
required
integer
>= 2
agreement_version
required
integer
>= 1

Example generated

{
"booking_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
"snapshot_seq": 1,
"agreement_version": 1
}

booking_not_found or no_agreement.

booking_cancelled.

reason_required.

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"
}