Contract v1 · generated reference

Event catalogue

Repository-backed outbox names and provider events; no invented commercial event is implied.

Command events are written to the outbox with the authoritative state change. Scheduler and provider observations are emitted only after a bounded authoritative read or verified ingress; they do not imply a commercial transition that did not commit.

availability.capacity_changed
booking.cancellation_requested
booking.disruption_reported
booking.refund_requested
booking.reschedule_requested
checkout.requested
group.created
group.decision.updated
group.invited
group.joined
group.message.sent
group.poll.created
group.poll.voted
hold.placed
holds.expiry_manual_reconciliation_required
listing.published
partner.business_details_submitted
partner.organization_created
partner.team_invited
payments.authorization_expiring
payments.commercial_authority_blocked
payments.manual_reconciliation_required
payments.unmatched_provider_event
quote.created
review.submitted
safety.reported
support.acknowledgement.requested.v1

Accepted provider payment events

payment_intent.amount_capturable_updated
payment_intent.canceled
payment_intent.payment_failed
payment_intent.succeeded

Consumers must tolerate duplicates and unknown future event types. They must not move state backward when a late provider event arrives.

Common integration contract

Sandbox and Production are isolated

Run examples only in a governed sandbox or local emulator. Sandbox identities, App Check tokens, payment fixtures and data do not grant Production access. The typed ports do not ratify a public numeric quota; enforcement may be stricter. Honor RATE_LIMITED and the server's retry-after value.

Authentication and authorization

Firebase Auth proves identity. App Check proves the approved app where a callable requires it. Roles, organization membership, requester identity and resource ownership are derived and rechecked by the server.

Authentication guide

Errors and recovery

Stable error codes distinguish validation, denial, conflict, expiry, authority pending, rate limiting and temporary unavailability. Never infer success from an HTTP redirect or a browser state.

Error catalogue

Idempotency, concurrency and retry

Reuse an idempotency key only for an identical retry. A new intent needs a new key. Preserve version preconditions and reload after a conflict.

Retry guidance

Changes and escalation

Check compatibility before adopting a new contract version. Review the changelog, service status and support guidance before retrying a persistent failure.

Changelog Service status Developer support

Common failure families
Family	Client decision
Authentication / authorization	Refresh or step up only when instructed; do not retry a denial unchanged.
Validation / conflict / expiry	Correct or reload state, then obtain confirmation for a new intent.
Rate limited / unavailable	Honor retry-after and use bounded backoff; inspect service status.
Unknown / server	Fail closed and escalate with a privacy-safe correlation id.

Executable network examples are published only when the exact wire schema is producer-proven. Check the selected operation's example-availability status; an unresolved schema is a release blocker, not permission to guess.

Verified examples and local-only recovery snippets