GrabaTable

[email protected]
Dashboard

Error Handling & Best Practices

Error Handling

The API uses standard HTTP status codes and returns JSON-formatted error messages.

401 Unauthorized

Invalid or missing API key

{"error": "Invalid API credentials"}

422 Validation Error

Invalid request data

{"error": "Validation failed", "messages": {}}

429 Rate Limit

Too many requests

{"error": "Rate limit exceeded"}

404 Not Found

Resource does not exist

{"error": "No availability found"}

Best Practices

Security

  • Never expose your API secret in client-side code or version control
  • Store credentials in environment variables
  • Rotate secrets every 3 months (you will receive warnings)
  • Use HTTPS for all requests

Performance

  • Choose the regional endpoint closest to your server
  • Cache venue and table data (changes infrequently)
  • Implement exponential backoff for rate limit errors
  • Monitor your daily request count to avoid hitting limits

Integration

  • Check availability before creating reservations
  • Store the reservation reference for customer service
  • Handle all error responses gracefully
  • Set appropriate timeouts (recommended: 10 seconds)

Need Help?

Our support team is here to help you integrate successfully.

×