Web Application Endpoints
BugSplat provides RESTful web services to access data on our backend. The BugSplat database should be selected using the "database" URL parameter. Data is returned in JSON format. Authentication is required for all endpoints. See the curl example at the end of this page for an illustration of this process.
Want to see our API in action? Open your web browser inspector to see how our web application uses the endpoints below!
Most API endpoints support a "database={name}" parameter to specify which BugSplat database to use. Without this parameter, the current (default) database will be selected.
DeprecatedCompanyCrashCrashesCrash GroupsDatabasesDefectEventsSupport ResponseSymbolsUser (GDPR)UsersVersionsCurl Example
You can access the web services with a variety of tools. The API authenticates with an OAuth2 Client ID and Client Secret, which you can create on the Integrations page. Here’s an example using Curl to exchange them for an access token and query the Fred database:
Access tokens expire after 24 hours. Request a new one with the same Client ID and Client Secret when yours expires.
Postman Collection
Several of our API endpoints can be tested via our public Postman collection.
First, click the top-level BugSplat collection folder, select the Variables tab, and input variables as necessary. Requests authenticate automatically when you provide values for client_id and client_secret generated on our Integrations page.
Special Rules for POST Requests
Requests authenticated with an OAuth2 bearer token don't need an XSRF token. The Authorization header is all a POST request needs.
Last updated
Was this helpful?
