Skip to content

Troubleshooting

SymptomCheck
401 Authentication requiredBearer header exists and session is not expired/logged out
403 Insufficient permissionMembership contains a role allowed for the operation
403 Attendee is outside the allowed groupsUser and instance group memberships overlap
409 Instance is not bookableInstance is scheduled and audience is not nobody
409 Instance is fullCapacity and confirmed bookings
409 Entitlement has expiredEntitlement expiry and server clock
402 Payment failedPayment gateway result and merchant configuration
Readiness failsDatabase connectivity, credentials, migrations, and application logs
/docs assets return 404VitePress base is /docs/ and npm run build:docs ran

API errors are JSON. Reverse-proxy, browser, or HTML errors usually indicate routing rather than domain validation.

When reporting a problem, include the request path, status, timestamp, environment, and correlation information available from the gateway—but never include magic-link tokens, sessions, database credentials, or payment secrets.

Booking SaaS implementation documentation