Skip Main Navigation
Page Content


When an error occurs during an API request, you’ll get a response with an error HTTP status (in the 400 or 500 range), as well as a JSON response containing more information about the error.

A typical error response looks like this:

    "error": "VENUE_AND_ONLINE",
    "error_description": "You cannot both specify a venue and set online_event",
    "status_code": 400

The error key contains a constant string value for error - in this case, VENUE_AND_ONLINE - and is what you should key your error handling off of, as this string won’t change depending on locale or as we change the API over time.

The error_description key is for developer information only and will usually contain a more informative explanation for the error, should you be confused. You should not display this string to your users; it’s often very technical and may not be localized to their language.

The status_code value just mirrors the HTTP status code you got as part of the request. It’s there as a convenience if your HTTP library makes it very hard to get status codes, or has one error handler for all error codes.

Some of the NOT_AUTHORIZED errors can optionally provide denied_permissions, a list of permissions that the calling user lacks, but are required to access the requested data or perform the requested action.

Common Errors

You can find a listing of the individual errors for each endpoint on their endpoint entries, but there are also some common errors that all endpoints might return:

  • NOT_FOUND: The URL you gave is not valid. Status code 404.
  • INVALID_AUTH: Your authentication (usually OAuth token) is incorrect. Status code 400.
  • INVALID_AUTH_HEADER: Your Authentication header is malformed. Status code 400.
  • NO_AUTH: You did not provide any authentication at all. Status code 401.
  • BAD_PAGE: The page number you gave does not exist or makes no sense (e.g. negative). Status code 400.
  • NOT_AUTHORIZED: The user you are connecting as is not allowed to view/perform that action. Status code 403.
  • METHOD_NOT_ALLOWED: You sent a method to the endpoint it can’t handle (e.g. DELETE to a GET-only endpoint). Status code 405.
  • HIT_RATE_LIMIT: You have hit your hourly rate limit for this token to the API. Default rate limits are set to 1,000 calls per hour. Status code 429.
  • INTERNAL_ERROR: An unhandled error occured in Eventbrite. Contact developer support if this persists. Status code 500.
  • EXPANSION_FAILED: There was an unhandled error trying to expand one of the specified expansions; the request is likely to succeed if you don’t ask for expansions, but contact developer support if this persists. Status code 500.
  • INVALID_BATCH: Your batched request was malformed or missing. Status code 400.