API integration

Use the origin hosting Booking SaaS and append /api. Preview examples use the current preview host; production consumers should use their deployment’s canonical domain.

export BOOKING_URL=https://booking.example.com

Verify availability

curl --fail "$BOOKING_URL/api/health/ready"

/api/health reports process liveness. /api/health/ready also reads persistence and is the appropriate deployment/load-balancer check.

Authenticate requests

After consuming a magic link, pass the returned session ID:

curl "$BOOKING_URL/api/me" \
  -H "Authorization: Bearer $BOOKING_SESSION"

Integration order

Implement consumers in this order:

1. Authentication and session storage.
2. Current-user/account retrieval with /api/me.
3. Event and instance listings.
4. Product display and purchase.
5. Booking creation, listing, and cancellation.
6. Administrative operations according to the current user’s roles.

Use Swagger UI to experiment and OpenAPI JSON for client generation. Generated clients must still handle 401, 403, 404, and 409 responses as normal domain outcomes.