Version 1 (decommissioned)

Access information about your organization, projects, errors, and more to build custom integrations.

This version of the Bugsnag API has been decommissioned. Please see the version 2 documentation.


Our data access API allows you to interact with various Bugsnag resources, including Accounts, Comments, Errors, Events, Projects, and Users.

  • API access is over HTTPS using the endpoint
  • Data is sent and received using JSON
  • Timestamps are returned in ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ


All requests to the Bugsnag API require authentication. To authenticate API requests you can either use your Bugsnag user credentials, or your account-wide auth token.

User credentials

To access the Bugsnag API as a user, you can use your Bugsnag user credentials via Basic Authentication. Simply send the email address and password associated with the user:

curl -u

Personal Auth Tokens

Alternatively you can authenticate by using Personal Auth Tokens, which you can generate in the My Account section of Bugsnag settings.

There are two ways to send this auth token with requests, you can send the token in an Authorization header:

$ curl -H "Authorization: token YOUR-TOKEN-HERE"

or, you can authenticate using a parameter:

$ curl

Organization credentials

You can authenticate as an Organization using your organization’s Data access API key, which you can find in the Organization section of your Bugsnag settings.

Organization API access keys are used the same way as Personal Auth tokens, but they map to the organization as a whole rather than a specific user.


Many API methods take optional parameters. For GET requests, any parameters not specified as a segment in the path can be passed as an HTTP query string parameter.

For POST, PATCH, and DELETE requests, parameters not included in the URL should be encoded as JSON with a Content-Type of ‘application/json’.

Response codes

  • Sending invalid JSON will result in a 400 Bad Request response
  • Sending the wrong type of JSON values will result in a 400 Bad Request response
  • Trying to access the API without authenticating or with an invalid auth token will result in a 401 Unauthorized response
  • Trying to access resources which do not exist will result in a 404 Not Found response
  • Trying to access resources which you do not have access to will result in a 404 Not Found response, in order to avoid disclosing the existence of user data

Hypermedia URLs

All API resources may have one or more *_url properties linking to other resources. These are meant to provide explicit URLs so that API clients don’t need to construct URLs on their own. It is highly recommended that API clients use these. Doing so will make future upgrades of the API easier for developers.


Pagination info is included in the Link header. It is important to follow these Link header values instead of constructing your own URLs since the pagination method can differ between resources.

The URL for pagination is shown inside angled brackets, and the type of pagination link is described in the rel field:

Link: <>; rel="next"

The possible values for rel are:

  • next - Shows the URL for the next page of results
  • prev - Shows the URL for the previous page of results