Skip to main content
The meetergo API uses standard HTTP status codes and returns structured error responses. This guide covers how to handle errors effectively.

Error Response Format

All errors follow this structure:

HTTP Status Codes

Success Codes

Client Error Codes

Server Error Codes

Common Errors and Solutions

Authentication Errors

Missing Authorization Header

Solution: Include the Authorization header:

Invalid API Key

Solution: Verify your API key is correct and complete.

Expired API Key

Solution: Create a new API key in the dashboard.

Missing User Header

Solution: Include the user context header:

Booking Errors

Time Slot Unavailable

Solution: Query fresh availability and select another slot.

Invalid Duration

Solution: Check the meeting type’s allowed durations before booking.

Missing Host

Solution: Provide either hostIds array or queueId for round-robin.

Validation Errors

Solution: Check the errors array for specific field issues.

Error Handling Patterns

JavaScript/TypeScript

Python

Retry Strategy

For transient errors (429, 5xx), implement exponential backoff:

Best Practices

Always check status codes - Don’t assume success
Log errors with context - Include request details for debugging
Use exponential backoff - For rate limits and server errors
Parse validation errors - Show specific field errors to users
Handle race conditions - Slots can be booked between availability query and booking
Don’t retry 4xx errors (except 429) - They indicate client issues that won’t resolve with retries