Skip to main content

Base URL

The Birdeye APIs are built on HTTP and are RESTful APIs.
  • Uses resource-oriented URLs.
  • Uses built-in HTTP capabilities for passing parameters and authentication.
  • Responds with standard HTTP response codes to indicate errors.
  • Requests and responses payload attached with all the mentioned APIs — you may choose your preferred language per the integration requirement.

Authentication and Rate Limiting

All API requests targeting business accounts must include the x-api-key header. This header is required and mandatory for successful authentication and access to the API endpoints.To protect your API key and prevent unauthorized access, please ensure all API requests are made from your backend server. Do not call the APIs directly from the browser or expose your API key in any client-side code.
To call a Birdeye API, you need a valid API key. It can be fetched via the Birdeye dashboard and is a confidential key. There is a limit to calling APIs with each API key — connect with the support team to get the current limit. If too many requests are made within the threshold timeframe, an error will be returned in the response. Every request must include the header:

Pagination

Multiple APIs support pagination via two parameters: sindex and count.
Deep pagination with a record window greater than 100,000 is not supported. Either reduce sindex + count to be less than or equal to 100,000, or use appropriate filters to narrow down your result set.
Example — fetch 20 records in two pages:
Example — fetch the 100,000th record:

HTTP Status Codes

Every API response will have an HTTP status code.

Error Response

Birdeye API will return a validation error in case of missing/invalid input in the request. The response will return the errorCode and errorMessage.

API Groups