OAuth2

BugSplat supports authenticating via OAuth2 in addition to the username/password authentication described in our API docs. Currently, only the OAuth2 client credentials flow is supported. If you are interested in other OAuth2 authentication methods, please reach out to [e-mail].

A reference client implementation can be found in our @bugsplat/js-api-client repo.

Client Credentials

To authenticate via OAuth2 client credentials you will need to create a Client Id and Client Secret pair on the OAuth Integrations page.

Adding a New Integration

Copy the Client Id and Client Secret to a secure location. Once you've dismissed the dialog the Client Secret will not be displayed again.

Authorize

The Client Id and Client Secret are used in a POST to the server and will return access_token and a token_type. The Authorize endpoint is described below.

Headers

Once an access_token and token_type have been acquired they can be used in any of the API requests outlined in our API docs. To make an authenticated request to one of BugSplat's API endpoints add a header with a key of Authorization and a value of ${token_type} ${access_token}.

Authorize

POST https://app.bugsplat.com/oauth2/authorize

Exchange a Client Id and Client Secret for a bearer token.

Request Body

Name	Type	Description
scope	string	OAuth2 scope, currently only restricted is the only available scope
client_secret	string	The Client Secret created above
client_id	string	The Client Id created above
grant_type	string	OAuth2 grant type, in this case, client_credentials

200

{
  "token_type": "Bearer",
  "expires_in": 3600,
  "access_token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9[...]"
}