Skip to main content

Bugsnag

Bugsnag is an application stability monitoring platform that automatically detects and reports errors in real time across web, mobile, and server-side applications. Built for engineering and development teams, Bugsnag captures exceptions, crashes, and unhandled errors with full stack traces, device context, and user breadcrumbs—giving teams the diagnostic information they need to prioritize and resolve issues quickly. With support for over 50 languages and frameworks, Bugsnag integrates into virtually any application stack and provides a centralized Data Access API for querying error events, projects, organizations, collaborators, and stability metrics.

Bugsnag icon

Power end-to-end data operations for your Bugsnag API with Nexla. Our bi-directional Bugsnag connector is purpose-built for Bugsnag, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Bugsnag or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Bugsnag workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Bugsnag Account​

A Bugsnag account is required to connect Nexla to your Bugsnag organization. Bugsnag offers plans for individuals and teams at bugsnag.com.

Generate a Personal Auth Token​

Nexla authenticates with the Bugsnag Data Access API using a Personal Auth Token tied to your Bugsnag user account. This token grants Nexla access to your organization's error data, projects, and related resources based on your account's permissions.

To generate a Personal Auth Token in Bugsnag:

  1. Sign in to your Bugsnag dashboard at app.bugsnag.com.

  2. Click your avatar or account name in the upper-right corner to open the account menu, and select My account settings.

  3. In the My account settings page, locate the Personal auth tokens section and click the Generate New Token link.

  4. Enter a descriptive name for the token in the Token description field — for example, Nexla Integration — so you can identify this token later.

  5. Click the Generate button to create the token.

Important

The generated token will only be displayed once. Copy the token value immediately and store it in a secure location (such as a password manager) before leaving the page. You will not be able to retrieve the token value again after navigating away.

  1. You can also navigate directly to the auth tokens page using the URL: https://app.bugsnag.com/settings/{your-organization-slug}/my-account/auth-tokens

Personal Auth Tokens are scoped to your Bugsnag user account and inherit your account's access permissions. The token provides access to all organizations and projects that your user account can access. For complete information about authentication options, see the Bugsnag Data Access API documentation.

Authenticate​

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Enter the Personal Auth Token you generated in your Bugsnag account settings in the Auth Token field. Nexla will use this token to authenticate all API requests to the Bugsnag Data Access API using the Authorization: token {auth_token} header format.

    Keep your Personal Auth Token secure and treat it like a password. If a token is compromised, you can revoke it at any time from the Personal auth tokens section of your Bugsnag account settings and generate a new one.

  4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Bugsnag connector tile, then select the credential that will be used to connect to the Bugsnag instance, and click Next; or, create a new Bugsnag credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Bugsnag endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

List Organizations

Retrieve all organizations associated with the authenticated user account.

  • Endpoint: GET https://api.bugsnag.com/user/organizations
  • Data path: $[*]

All parameters are optional; omitting filters returns all available records.

List Projects

Retrieve all projects for a given organization.

  • Endpoint: GET https://api.bugsnag.com/organizations/{parameter}/projects
  • Data path: $[*]
  • Organization ID (Required): The Bugsnag organization ID to retrieve projects for.

The Organization ID parameter is required to identify the specific resource to retrieve.

List Errors

Retrieve error groups for a project with optional status and date filters.

  • Endpoint: GET https://api.bugsnag.com/projects/{parameter}/errors?status={parameter}&sort={parameter}
  • Data path: $[*]
  • Project ID (Required): The Bugsnag project ID to retrieve errors for.
  • Status (Optional): Filter errors by status. Accepted values: 'open', 'fixed', 'ignored', 'snoozed'.
  • Sort (Optional): Sort errors by field. Accepted values: 'events', 'users', 'last_seen', 'first_seen'.

The Project ID parameter is required to identify the specific resource to retrieve.

List Events for Error

Retrieve individual error event occurrences for a specific error group.

  • Endpoint: GET https://api.bugsnag.com/projects/{parameter}/errors/{parameter}/events
  • Data path: $[*]
  • Project ID (Required): The Bugsnag project ID.
  • Error ID (Required): The Bugsnag error group ID to retrieve events for.

The Project ID parameter is required to identify the specific resource to retrieve.

List Releases

Retrieve application release history for a project including build metadata and error rates.

  • Endpoint: GET https://api.bugsnag.com/projects/{parameter}/releases
  • Data path: $[*]
  • Project ID (Required): The Bugsnag project ID to retrieve releases for.

The Project ID parameter is required to identify the specific resource to retrieve.

List Collaborators

Retrieve all collaborators (team members) for an organization.

  • Endpoint: GET https://api.bugsnag.com/organizations/{parameter}/collaborators
  • Data path: $[*]
  • Organization ID (Required): The Bugsnag organization ID to retrieve collaborators for.

The Organization ID parameter is required to identify the specific resource to retrieve.

List Stability Trend

Retrieve application stability trend data showing session and error rates over time.

  • Endpoint: GET https://api.bugsnag.com/projects/{parameter}/stability_trend
  • Data path: $.buckets[*]
  • Project ID (Required): The Bugsnag project ID to retrieve stability data for.

The Project ID parameter is required to identify the specific resource to retrieve.

Get Pivot Report

Retrieve aggregated error event counts grouped by a specified dimension (e.g., app version, OS, user).

  • Endpoint: GET https://api.bugsnag.com/projects/{parameter}/pivot/trend?dimension={parameter}
  • Data path: $.data[*]
  • Project ID (Required): The Bugsnag project ID to generate the pivot report for.
  • Dimension (Optional): The dimension to pivot by. Accepted values: 'app_version', 'os_version', 'user_id', 'context'.

The Project ID parameter is required to identify the specific resource to retrieve.

List Event Fields

Retrieve available custom metadata field keys observed in error events for a project.

  • Endpoint: GET https://api.bugsnag.com/projects/{parameter}/event_fields
  • Data path: $[*]
  • Project ID (Required): The Bugsnag project ID to retrieve event fields for.

The Project ID parameter is required to identify the specific resource to retrieve.

List Trends

Retrieve error event volume trend data over time for a project for monitoring error rates.

  • Endpoint: GET https://api.bugsnag.com/projects/{parameter}/trend
  • Data path: $.data[*]
  • Project ID (Required): The Bugsnag project ID to retrieve trend data for.

The Project ID parameter is required to identify the specific resource to retrieve.

Get Project

Retrieve detailed configuration and metadata for a specific Bugsnag project.

  • Endpoint: GET https://api.bugsnag.com/projects/{parameter}
  • Data path: $
  • Project ID (Required): The Bugsnag project ID to retrieve details for.

The Project ID parameter is required to identify the specific resource to retrieve.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration​

Bugsnag data sources can also be manually configured to ingest data from any valid Bugsnag Data Access API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or sources that require custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

The Bugsnag Data Access API base URL is https://api.bugsnag.com, and all endpoints require authentication via the Personal Auth Token configured in your Bugsnag credential. Most list endpoints return a top-level JSON array, so the path to data is typically $[*]. You do not need to add the Authorization header manually — Nexla applies it from your credential; optional headers such as X-Version and Accept can be added if a specific endpoint requires them. Date/time macros can be used to filter by date — for example, ?filters[event.since][][type]=eq&filters[event.since][][value]={now-1} retrieves errors reported since the previous time period, using ISO 8601 date-time format.

The Bugsnag Data Access API enforces rate limits over a 1-minute window. If a request fails with an HTTP 429 response, wait briefly before retrying; the X-RateLimit-Limit and X-RateLimit-Remaining response headers indicate your current usage. For a complete list of available endpoints, refer to the Bugsnag API reference.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Bugsnag data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.