Error Codes & Troubleshooting
A complete reference of all system, API, and booking-related error codes. Use the search bar or filters to find specific codes.
| Code | Category | Status/Severity | Message | Description & Resolution |
|---|---|---|---|---|
| 400 | HTTP/API | Client Error | Bad Request | Malformed request syntax or invalid parameters. Verify payload structure and required fields match the API schema. Check console/network logs for exact field validation errors. |
| 401 | HTTP/API | Client Error | Unauthorized | Missing or invalid API key/authentication token. Ensure the `Authorization: Bearer |
| 403 | HTTP/API | Permission | Forbidden | Valid credentials but insufficient permissions. Verify the API key has the required scope (e.g., `bookings:write`, `payments:read`). Contact account admin to elevate access. |
| 404 | HTTP/API | Not Found | Resource Not Found | Endpoint or booking ID does not exist. Double-check resource UUIDs, base URL, and version parameters. Deleted/soft-removed resources return 404 after 30-day grace period. |
| 409 | HTTP/API | Conflict | Booking Conflict | Time slot is already reserved or calendar sync conflict detected. Use the availability endpoint to check real-time slots before creating bookings. Implement exponential backoff for retries. |
| 422 | HTTP/API | Validation | Unprocessable Entity | Request was well-formed but contained semantic/business rule errors (e.g., past date, invalid timezone, guest limit exceeded). Review the `errors[]` array in the response body for field-level details. |
| 429 | HTTP/API | Rate Limit | Too Many Requests | API rate limit exceeded. Free tier: 60 req/min. Pro: 300 req/min. Business: 1000 req/min. Implement client-side throttling and respect `Retry-After` header. |
| 500 | HTTP/API | Server Error | Internal Server Error | Unexpected failure on BookEase infrastructure. This is not your fault. Include the `X-Request-ID` header in your support ticket. Retry with backoff; persistent issues will be investigated by our SRE team. |
| BE-101 | Platform | System | Calendar Sync Timeout | Google/Outlook/Microsoft calendar sync failed to respond within 5s. Clear local cache, revoke/reauthorize calendar OAuth token, and verify webhook delivery to your sync endpoint. |
| BE-102 | Platform | Critical | Provider Unavailable | Selected service provider has temporarily disabled booking or is outside service hours. Notify the provider to update availability settings or switch to backup providers in your routing config. |
| BE-103 | Platform | Info | Reminder Delivery Delayed | SMS/Email reminder batch processing queue is backed up. Messages will deliver within 15-30 mins. No action needed unless SLA breach occurs. Check dashboard notification logs. |
| PAY-201 | Payment | Declined | Card Payment Failed | Payment gateway declined the transaction due to insufficient funds, expired card, or fraud filter trigger. Request alternative payment method or advise customer to contact their bank. |
| PAY-202 | Payment | Gateway | Processor Timeout | Stripe/Adyen response exceeded 10s timeout. Check if the payment succeeded idempotently before retrying. Use idempotency keys to prevent duplicate charges. |
| PAY-203 | Payment | Compliance | 3D Secure Required | Bank requires additional verification. Redirect user to 3DS flow via the provided `authentication_url`. Do not mark booking as paid until `payment_intent` status is `succeeded`. |
| AUTH-301 | Authentication | Invalid | Expired Session Token | JWT or session cookie has expired (default: 24h). Trigger silent refresh via `/auth/refresh` endpoint or redirect to login page. Ensure clock skew is < 30s on client devices. |
| AUTH-302 | Authentication | Security | IP Mismatch Detected | Login attempted from new region/device triggering fraud protection. Verify user identity via email/SMS OTP, then whitelist the IP or adjust security policy in admin dashboard. |
| AUTH-303 | Authentication | Locked | Account Temporarily Locked | Too many failed login attempts (5 in 10 mins). Account auto-unlocks after 15 mins. Use password reset flow or contact support if legitimate access is blocked. |
No matching error codes found
Try adjusting your search terms or switching to a different category filter.