Bugsnag integration: operations for AI agents
Bugsnag connects to Type.com as an integration. This page lists the 156 operations documented for Claude and Codex in Type.com: 78 read, 33 write, 45 destructive.
About Bugsnag
Bugsnag is an error monitoring and stability management platform that helps developers identify, prioritize, and fix software bugs.
Categories: Developer Tools & IT
How to connect Bugsnag to Type.com
- Access
- Organization connection: one shared account for the workspace.
To add the connection, follow the steps in Space connections.
Documented operations
156 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.
156 operations listed.
data-access / Current User
- Read
List the Current User's Organizations
List the Current User's Organizations. Inputs include admin, per_page.
GET /user/organizations - Read
List Saved Searches on a Project
Returns the saved searches for a given project sorted by name in lexicographic order. Inputs include project_id, shared.
GET /projects/{project_id}/saved_searches - Read
Get a Saved Search
Get a Saved Search. Inputs include id.
GET /saved_searches/{id} - Read
Get the Usage Summary for a Saved Search
Returns a short usage summary for a saved search. Inputs include id.
GET /saved_searches/{id}/usage_summary - Read
List an Organization's Projects
Returns a list of projects for the given organization. Inputs include organization_id, q, sort, direction, per_page.
GET /organizations/{organization_id}/projects - Write
Create a Saved Search
Create a Saved Search. Inputs include project_id, name, filters, filters.user.id, filters.user.id[].type.
POST /saved_searches - Write
Update a Saved Search
Update a Saved Search. Inputs include id, name, filters, filters.user.id, filters.user.id[].type.
PATCH /saved_searches/{id} - Destructive
Delete a Saved Search
Delete a Saved Search. Inputs include id.
DELETE /saved_searches/{id}
data-access / Projects
- Read
View a Project
View a Project. Inputs include project_id.
GET /projects/{project_id} - Read
List the Event Fields for a Project
Event fields are the fields on event resources that can be used for filtering. This includes built-in fields and any custom filters. The event fields supported vary by project type. Inputs include project_id.
GET /projects/{project_id}/event_fields - Read
List Release Groups on a Project
List Release Groups on a Project. Inputs include project_id, release_stage_name, top_only, visible_only, per_page.
GET /projects/{project_id}/release_groups - Read
Retrieve a Release Group
Retrieve a Release Group. Inputs include id.
GET /release_groups/{id} - Read
List Releases on a Project
A release models a particular application version running in a particular release stage. In the case of mobile projects, a release is also associated with a version code or bundle version. To learn more, see the following resources on the releases dashboard and build tool integrations. Inputs include project_id, release_stage, base, sort, offset.
GET /projects/{project_id}/releases - Read
View a Release
View a Release. Inputs include project_id, release_id.
GET /projects/{project_id}/releases/{release_id} - Read
List Releases on a Release Group
List Releases on a Release Group. Inputs include release_group_id, per_page, page_token.
GET /release_groups/{release_group_id}/releases - Read
View the stability trend for a project
Request the trend of unhandled session information (grouped by UTC day) in the last 30 days for the project's primary release stage. Inputs include project_id.
GET /projects/{project_id}/stability_trend - Read
Check the status of an event data request
Check the status of an event data request. Inputs include project_id, id.
GET /projects/{project_id}/event_data_requests/{id} - Read
Check the status of an event deletion request
Check the status of an event deletion request. Inputs include project_id, id.
GET /projects/{project_id}/event_data_deletions/{id} - Read
List Feature Flags on a Project
List Feature Flags on a Project. Inputs include project_id, release_stage_name, starred_at_top, include_variant_summary, q.
GET /projects/{project_id}/feature_flags - Read
List Feature Flag Summaries for a Project
List Feature Flag Summaries for a Project. Inputs include project_id, q, per_page.
GET /projects/{project_id}/feature_flag_summaries - Read
Get a Feature Flag
Get a Feature Flag. Inputs include id, project_id, release_stage_name, include_variant_summary.
GET /projects/{project_id}/feature_flags/{id} - Read
Get a Feature Flag's Error Overview
Get a Feature Flag's Error Overview. Inputs include id, project_id, release_stage_name.
GET /projects/{project_id}/feature_flags/{id}/error_overview - Read
Get a Feature Flag Variant's Error Overview
Get a Feature Flag Variant's Error Overview. Inputs include id, project_id, variant_ids, release_stage_name.
GET /projects/{project_id}/feature_flags/{id}/variants/error_overview - Read
List Variants on a Feature Flag by ID
List Variants on a Feature Flag by ID. Inputs include id, project_id, release_stage_name, q, per_page.
GET /projects/{project_id}/feature_flags/{id}/variants - Read
List Variants on a Feature Flag by name
List Variants on a Feature Flag by name. Inputs include name, project_id, release_stage_name, q, per_page.
GET /projects/{project_id}/feature_flags/by_name/{name}/variants - Read
List Span Groups on a Project
If there are no Span Groups, it returns an empty array. Inputs include project_id, sort, direction, per_page, offset.
GET /projects/{project_id}/span_groups - Read
Show a Span Group
If there are no spans in the requested group, it will show a span group with an empty statistics attribute. Inputs include project_id, id, filters.
GET /projects/{project_id}/span_groups/{id} - Read
List Span Group Summaries for a Project
List Span Group Summaries for a Project. Inputs include project_id, per_page, offset, filters.
GET /projects/{project_id}/span_group_summaries - Read
Get a Span Group's timeline
Get a Span Group's timeline. Inputs include project_id, id, filters.
GET /projects/{project_id}/span_groups/{id}/timeline - Read
Get a Span Group's distribution
Get a Span Group's distribution. Inputs include project_id, id, filters.
GET /projects/{project_id}/span_groups/{id}/distribution - Read
List the starred Span Group descriptions
List the names and properties of the requesting user's starred Span Groups for a project and optionally performance categories. Inputs include project_id, categories, per_page, offset.
GET /projects/{project_id}/starred_span_groups - Read
List Performance Targets for a Span Group by ID
List Performance Targets for a Span Group by ID. Inputs include project_id, id.
GET /projects/{project_id}/span_groups/{id}/performance_targets - Read
Get Spans for a Span Group
Get Spans for a Span Group. Inputs include project_id, category, name.
GET /projects/{project_id}/span_group_categories/{category}/span_groups/{name}/spans - Read
List Spans for a Span Group by ID
List Spans for a Span Group by ID. Inputs include project_id, id, filters, sort, direction.
GET /projects/{project_id}/span_groups/{id}/spans - Read
List Spans for a Trace
List Spans for a Trace. Inputs include project_id, trace_id, from, to, target_span_id.
GET /projects/{project_id}/traces/{trace_id}/spans - Read
List Page Load Span Groups
List Page Load Span Groups. Inputs include project_id, sort, direction, per_page, offset.
GET /projects/{project_id}/page_load_span_groups - Read
Show a Page Load Span Group by ID
Show a Page Load Span Group by ID. Inputs include project_id, id, filters.
GET /projects/{project_id}/page_load_span_groups/{id} - Read
List the Trace Fields on a project
Trace fields are the fields used for filtering spans that are aggregated in span groups on a project. They include a name identifier and filter options for each field. See Filtering for more information. Inputs include project_id.
GET /projects/{project_id}/trace_fields - Read
List a Project's Network Grouping Ruleset
List a Project's Network Grouping Ruleset. Inputs include project_id.
GET /projects/{project_id}/network_endpoint_grouping - Read
Get Performance Score Overview for Project
Retrieve the performance score for a specific project. Inputs include project_id, release_stage_name.
GET /projects/{project_id}/performance_overview - Write
Create a Project in an Organization
Create a Project in an Organization. Inputs include organization_id, name, type, ignore_old_browsers.
POST /organizations/{organization_id}/projects - Write
Create a custom Event Field
Create a custom Event Field. Inputs include project_id, path, reindex, filter_options, filter_options.name.
POST /projects/{project_id}/event_fields - Write
Update a custom Event Field
Update a custom Event Field. Inputs include project_id, display_id, path, reindex, filter_options.
PATCH /projects/{project_id}/event_fields/{display_id} - Write
Update a Release Group
Update a Release Group. Inputs include id, visible.
PATCH /release_groups/{id} - Write
Create an event data request
Request event data for the given project. This request will start an asynchronous job to collate all event data present at the time of the request and return a URL where you can download the data when the job is complete. These endpoints are intended for bulk download of events. If you want to query events, use the Events APIs instead. Inputs include project_id, report_type, filters, filters.user.id, filters.user.id[].type.
POST /projects/{project_id}/event_data_requests - Write
Star a Feature Flag
Star a Feature Flag. Inputs include project_id, feature_flag_id.
POST /user/projects/{project_id}/starred_feature_flags - Write
Update Span Group
Update Span Group. Inputs include project_id, id, is_starred.
PATCH /projects/{project_id}/span_groups/{id} - Destructive
Update a Project
Update a Project. Inputs include project_id, name, global_grouping, location_grouping, discarded_app_versions.
PATCH /projects/{project_id} - Destructive
Delete a Project
Delete a Project. Inputs include project_id.
DELETE /projects/{project_id} - Destructive
Regenerate a Project's notifier API key
Generate a new notifier API key for a project. This API key is used to configure the notifier library being used to report errors in the project. After regenerating a Project's notifier API key, your platform-specific notifier will need its configuration updated to use the new key. The previous key will not be supported. Inputs include project_id.
DELETE /projects/{project_id}/api_key - Destructive
Regenerate a Project's upload API key
Generate a new upload API key for a project. This API key is used to authenticate file upload requests (source maps, proguard files, etc.). After regenerating a Project's upload API key, your upload scripts will need to be updated to use the new key. The previous key will not be supported. Inputs include project_id.
DELETE /projects/{project_id}/upload_api_key - Destructive
Delete a custom Event Field
Delete a custom Event Field. Inputs include project_id, display_id.
DELETE /projects/{project_id}/event_fields/{display_id} - Destructive
Create an event deletion request
Creates a request to asynchronously delete events for the project. Note that filters such as user.email and user.name use substring matching, so using the user.id filter will be more appropriate for deleting events for 1 specific user. Inputs include project_id, skip_confirmation, filters, filters.user.id, filters.user.id[].type.
POST /projects/{project_id}/event_data_deletions - Destructive
Confirm an event deletion request
Confirm an event deletion request. Inputs include project_id, id.
POST /projects/{project_id}/event_data_deletions/{id}/confirm - Destructive
Delete a Feature Flag
Delete a Feature Flag. Inputs include project_id, id.
DELETE /projects/{project_id}/feature_flags/{id} - Destructive
Unstar a Feature Flag
Unstar a Feature Flag. Inputs include project_id, id.
DELETE /user/projects/{project_id}/starred_feature_flags/{id} - Destructive
Replace the ErrorAssignmentRules on a project
Replaces all the ErrorAssignmentRules on the project with the rules supplied rules. If no rules are supplied, all rules on the project are deleted. Inputs include project_id, assignment_rules, assignment_rules[].assignee, assignment_rules[].assignee.type, assignment_rules[].assignee.id.
PUT /projects/{project_id}/error_assignment_rules - Destructive
Update a Project's Network Grouping Ruleset
Update a Project's Network Grouping Ruleset. Inputs include project_id, endpoints.
PUT /projects/{project_id}/network_endpoint_grouping
data-access / Errors
- Read
List the Errors on a Project
Get a list of the errors on a project. If you require a feed of all new errors as they are reported consider setting up a webhook integration instead. Inputs include project_id, base, sort, direction, per_page.
GET /projects/{project_id}/errors - Read
View an Error
View an Error. Inputs include project_id, error_id, filters, filter_groups, filter_groups_join.
GET /projects/{project_id}/errors/{error_id} - Read
View an Event
Note that event objects can include custom metadata and diagnostic fields configured directly in your app or added by the notifier library. The API preserves the original casing and key format as received, so any casing, including both snake_case and camelCase, may be valid for some fields. Inputs include project_id, event_id.
GET /projects/{project_id}/events/{event_id} - Read
List the Events on an Error
Get a list of the events of an error. If you require a feed of all new events as they are reported consider setting up a webhook integration instead. Inputs include project_id, error_id, base, sort, direction.
GET /projects/{project_id}/errors/{error_id}/events - Read
View the latest Event on an Error
View the latest Event on an Error. Inputs include error_id.
GET /errors/{error_id}/latest_event - Read
List the Events on a Project
List the Events on a Project. Inputs include project_id, base, sort, direction, per_page.
GET /projects/{project_id}/events - Read
List the Trends for an Error
Counts for an Error in a given time range, suitable for drawing histograms. Will return a maximum of 50 buckets (when using buckets_count) or 2000 data points (when using resolution). Inputs include project_id, error_id, filters, filter_groups, filter_groups_join.
GET /projects/{project_id}/errors/{error_id}/trends - Read
List the Trends for a Project
Counts for a Project in a given time range, suitable for drawing histograms. Will return a maximum of 50 buckets (when using buckets_count) or 2000 data points (when using resolution). Inputs include project_id, filters, filter_groups, filter_groups_join, buckets_count.
GET /projects/{project_id}/trends - Read
List Pivots on an Error
List Pivots on an Error. Inputs include project_id, error_id, filters, filter_groups, filter_groups_join.
GET /projects/{project_id}/errors/{error_id}/pivots - Read
List values of a Pivot on an Error
List values of a Pivot on an Error. Inputs include project_id, error_id, event_field_display_id, filters, filter_groups.
GET /projects/{project_id}/errors/{error_id}/pivots/{event_field_display_id}/values - Read
List Pivots on a Project
List Pivots on a Project. Inputs include project_id, filters, filter_groups, filter_groups_join, summary_size.
GET /projects/{project_id}/pivots - Read
List values of a Pivot on a Project
List values of a Pivot on a Project. Inputs include project_id, event_field_display_id, filters, filter_groups, filter_groups_join.
GET /projects/{project_id}/pivots/{event_field_display_id}/values - Read
List Comments on an Error
Collaborators are able to comment on Errors to add details, context, and work together toward a fix. Inputs include project_id, error_id, sort, direction, per_page.
GET /projects/{project_id}/errors/{error_id}/comments - Write
Update a Comment
Requires user authentication as only the author is able to update their comments. Inputs include comment_id, message.
PATCH /comments/{comment_id} - Write
Create a Comment on an Error
Requires user authentication as the user who will be the author of the comment. Inputs include project_id, error_id, message.
POST /projects/{project_id}/errors/{error_id}/comments - Destructive
Bulk Update Errors
Bulk Update Errors. Inputs include project_id, error_ids, severity, operation, assigned_collaborator_id.
PATCH /projects/{project_id}/errors - Destructive
Delete all Errors in a Project
Deletes all Error and Event data in a project. Use with caution. This action cannot be reversed. Inputs include project_id.
DELETE /projects/{project_id}/errors - Destructive
Update an Error
Update an Error. Inputs include project_id, error_id, severity, operation, assigned_collaborator_id.
PATCH /projects/{project_id}/errors/{error_id} - Destructive
Delete an Error
Delete an Error. Inputs include project_id, error_id.
DELETE /projects/{project_id}/errors/{error_id} - Destructive
Delete an Event
Delete an Event. Inputs include project_id, event_id.
DELETE /projects/{project_id}/events/{event_id} - Destructive
Delete a Comment
Delete a Comment. Inputs include comment_id.
DELETE /comments/{comment_id}
data-access / Integrations
- Read
List the supported Integrations
Get information about all the integrations supported and how they can be configured. This includes details of the fields needed to set them up.
GET /integrations - Read
Get a Configured Integration
Get the full description of a configured integration. Inputs include id.
GET /configured_integrations/{id} - Read
List Summaries of the Configured Integrations for a Project
List summaries of all the configured integrations on a project. Summaries are lightweight descriptions of a configured integration. For a full description, use the Get a Configured Integration endpoint. Inputs include project_id, per_page, page_token, category.
GET /projects/{project_id}/configured_integration_summaries - Read
List the Integration Connections for an Organization
List the Integration Connections for an Organization. Inputs include organization_id, type.
GET /organizations/{organization_id}/integration_connections - Write
Test an Integration
Test an integration using the configuration parameters provided without saving it as a configured integration. For issue-tracker integrations this will created a test issue. For team-notification, data-forwarding and on-call notifications it will send a test alert/message. Use the Configured Integrations test endpoint for integrations which are already configured. Inputs include key, configuration, configuration.user_name, configuration.project_id, configuration.password.
POST /integrations/test - Write
Update a Configured Integration
Update the configuration for an integration on a project. Inputs include id, configuration, configuration.user_name, configuration.project_id, configuration.password.
PATCH /configured_integrations/{id} - Write
Update a Configured Integration's Trigger Config
Set a condition for automatic integration behavior. Inputs include id, trigger_config_key, active, settings, settings[].saved_search_id.
PATCH /configured_integrations/{id}/trigger_configs/{trigger_config_key} - Write
Test a Configured Integration
Test a configured integration. For issue-tracker integrations this will create a test issue. For team-notification, data-forwarding and on-call notifications it will send a test alert/message. To test an integration without saving the configuration first, use /integrations/test. Inputs include id, component, customFields, host, ignore_tls_validation.
POST /configured_integrations/{id}/test - Write
Configure an Integration
Configure a new integration for a project. Only one issue-tracker-type integration is allowed on a project, unless your plan supports multiple issue trackers. Inputs include project_id, integration_key, configuration, configuration.user_name, configuration.project_id.
POST /projects/{project_id}/configured_integrations - Destructive
Delete a Configured Integration
Delete the configuration for an integration. Inputs include id.
DELETE /configured_integrations/{id}
data-access / Organizations
- Read
View an Organization
View an Organization. Inputs include id.
GET /organizations/{id} - Read
List all collaborators that are members of your organization
List all collaborators that are members of your organization. Inputs include organization_id, per_page, q.
GET /organizations/{organization_id}/collaborators - Read
Show a Collaborator on an Organization
Show a Collaborator on an Organization. Inputs include organization_id, id.
GET /organizations/{organization_id}/collaborators/{id} - Read
List Collaborators on a Project
List all collaborators that have access to a project. Inputs include project_id, per_page.
GET /projects/{project_id}/collaborators - Read
Show a collaborator in a project.
Show a collaborator in a project. Requires requesting user to have access to the given project. Inputs include project_id, id.
GET /projects/{project_id}/collaborators/{id} - Read
View the project count of a collaborator
View the project count of a collaborator Inputs include organization_id, collaborator_ids.
GET /organizations/{organization_id}/collaborators/project_access_counts - Read
View Projects a Collaborator has access to
View Projects a Collaborator has access to Inputs include organization_id, collaborator_id, q, sort, direction.
GET /organizations/{organization_id}/collaborators/{collaborator_id}/projects - Read
List project accesses for a collaborator
List all projects a collaborator has access to within an organization. Inputs include organization_id, collaborator_id, per_page.
GET /organizations/{organization_id}/collaborators/{collaborator_id}/project_accesses - Read
Show a Collaborator's Access Details for a Project
Return the details of a collaborator's access to a project. Inputs include organization_id, collaborator_id, project_id.
GET /organizations/{organization_id}/collaborators/{collaborator_id}/project_accesses/{project_id} - Read
List Teams from a query
List Teams from a query. Inputs include organization_id, q, per_page, offset.
GET /organizations/{organization_id}/teams - Read
Show the details of a team
Show the details of a team. Inputs include organization_id, id.
GET /organizations/{organization_id}/teams/{id} - Read
List Suggested Collaborators to Add to a Team
List Suggested Collaborators to Add to a Team. Inputs include organization_id, id, q, include_has_access, per_page.
GET /organizations/{organization_id}/teams/{id}/suggested_collaborators - Read
List Teams for a Collaborator
List Teams for a Collaborator. Inputs include organization_id, id, q, per_page, offset.
GET /organizations/{organization_id}/collaborators/{id}/teams - Read
List Suggested Teams for a Collaborator
List Suggested Teams for a Collaborator. Inputs include organization_id, id, q, include_is_member, per_page.
GET /organizations/{organization_id}/collaborators/{id}/suggested_teams - Read
List the Collaborators in a Team
List the Collaborators in a Team. Inputs include organization_id, id, q, per_page, offset.
GET /organizations/{organization_id}/teams/{id}/collaborators - Read
List Project Access for a Team
List Project Access for a Team. Inputs include organization_id, id, q, per_page, offset.
GET /organizations/{organization_id}/teams/{id}/project_accesses - Read
Suggest Projects to Add to a Team
Suggest a list of projects from the organization that the team could be given access to. Inputs include organization_id, id, include_has_access, q, per_page.
GET /organizations/{organization_id}/teams/{id}/suggested_projects - Read
Check the status of an event data request
Check the status of an event data request. Inputs include organization_id, id.
GET /organizations/{organization_id}/event_data_requests/{id} - Read
Check the status of an event deletion request
Check the status of an event deletion request. Inputs include organization_id, id.
GET /organizations/{organization_id}/event_data_deletions/{id} - Read
List Spans for a Trace
Returns the spans for a trace at an organizational level. Access to this endpoint is restricted on the distributed traces view permission. Inputs include organization_id, trace_id, from, to, target_span_id.
GET /organizations/{organization_id}/traces/{trace_id}/spans - Write
Create an Organization
Creates a new Bugsnag organization and adds the current user to it as an admin. Requires user authentication as the initial user of the organization. Inputs include name.
POST /organizations - Write
Update an Organization
Update an Organization. Inputs include id, name, billing_emails, auto_upgrade, invoice_address.
PATCH /organizations/{id} - Write
Invite a collaborator to your organization
Invite a collaborator to your organization. Inputs include organization_id, email, name, password, project_ids.
POST /organizations/{organization_id}/collaborators - Write
Bulk invite collaborators to your organization
Bulk invite collaborators to your organization. Inputs include organization_id, emails, project_ids, project_roles, project_roles.{key}.
POST /organizations/{organization_id}/collaborators/bulk_invite - Write
Add a collaborator to a group of Teams
Add a collaborator to a list of teams, or all a collaborator to all the teams in this organization. Inputs include organization_id, id, team_ids, add_all_teams.
POST /organizations/{organization_id}/collaborators/{id}/team_memberships - Write
Create a Team
Create a Team. Inputs include organization_id, name.
POST /organizations/{organization_id}/teams - Write
Update a team name
Update a team name. Inputs include organization_id, id, name.
PATCH /organizations/{organization_id}/teams/{id} - Write
Add Collaborators to a Team
Add Collaborators to a Team. Inputs include organization_id, id, collaborator_ids, add_all_collaborators.
POST /organizations/{organization_id}/teams/{id}/team_memberships - Write
Add Project Access to a Team
Add Project Access to a Team. Inputs include organization_id, id, add_all_projects, project_role, project_roles.
PATCH /organizations/{organization_id}/teams/{id}/project_accesses - Write
Create an event data request
Request event data for the given organization. This request will start an asynchronous job to collate all event data present at the time of the request and return a URL where you can download the data when the job is complete. These endpoints are intended for bulk download of events. If you want to query events, use the Events APIs instead. Inputs include organization_id, report_type, filters, filters.user.id, filters.user.id[].type.
POST /organizations/{organization_id}/event_data_requests - Destructive
Delete an Organization
Delete an Organization. Inputs include id.
DELETE /organizations/{id} - Destructive
Regenerate an Organization's API key
Regenerate an Organization's API key. Inputs include id.
DELETE /organizations/{id}/api_key - Destructive
Regenerate an Organization's auth token
Deprecated. Use user-level authentication tokens instead.\nGenerate a new data access API auth token for the organization. This token allows you to read data from and write data to Bugsnag relating to your Organization, Projects, Errors, etc. After regenerating the auth token, the prior data access API auth token will no longer be supported. Inputs include id.
DELETE /organizations/{id}/auth_token - Destructive
Update a Collaborator's permissions
Update a Collaborator's permissions. Inputs include organization_id, id, project_ids, project_roles, project_roles.{key}.
PATCH /organizations/{organization_id}/collaborators/{id} - Destructive
Delete a Collaborator
Delete a Collaborator. Inputs include organization_id, id.
DELETE /organizations/{organization_id}/collaborators/{id} - Destructive
Remove a Collaborator from a group of Teams
Remove a collaborator from a group of teams. The request body for this operation should be documented here: The request body would have matched the TeamIDRequest schema, but DELETE operations cannot have a request body in OpenAPI3. Example: { "team_ids": ["team_id_1", "team_id_2"] } Inputs include organization_id, id.
DELETE /organizations/{organization_id}/collaborators/{id}/team_memberships - Destructive
Delete a team
Delete a team. Inputs include organization_id, id.
DELETE /organizations/{organization_id}/teams/{id} - Destructive
Remove Collaborators from a Team
Request body requires a CollaboratorsRequest object with the following properties: - user_ids: array of user IDs to remove from the team Inputs include organization_id, id.
DELETE /organizations/{organization_id}/teams/{id}/team_memberships - Destructive
Remove Project Access from a Team
Request body requires a TeamProjectAccessesDelete object with the following properties: - project_ids: array of project IDs to remove access from Inputs include organization_id, id.
DELETE /organizations/{organization_id}/teams/{id}/project_accesses - Destructive
Create an event deletion request
Creates a request to asynchronously delete events for the organization. Note that filters such as user.email and user.name use substring matching, so using the user.id filter will be more appropriate for deleting events for 1 specific user. Inputs include organization_id, skip_confirmation, filters, filters.user.id, filters.user.id[].type.
POST /organizations/{organization_id}/event_data_deletions - Destructive
Confirm an event deletion request
Confirm an event deletion request. Inputs include organization_id, id.
POST /organizations/{organization_id}/event_data_deletions/{id}/confirm
data-access / SCIM
- Read
List Collaborators on an Organization
Return the list of users for the organization. Inputs include organization_id, filter, startIndex, itemsPerPage.
GET /organizations/{organization_id}/scim/v2/Users - Read
Show a Collaborator on an Organization
Show a Collaborator on an Organization. Inputs include organization_id, id.
GET /organizations/{organization_id}/scim/v2/Users/{id} - Read
List Groups on an Organization
Return the list of groups for an organization. Inputs include organization_id, filter, startIndex, itemsPerPage.
GET /organizations/{organization_id}/scim/v2/Groups - Read
Show Group on an Organization
Show Group on an Organization. Inputs include organization_id, id.
GET /organizations/{organization_id}/scim/v2/Groups/{id} - Write
Create a Collaborator
Create a Collaborator. Inputs include organization_id.
POST /organizations/{organization_id}/scim/v2/Users - Write
Create Group on an Organization
This endpoint is used to add a group to your BugSnag organization. Inputs include organization_id, displayName.
POST /organizations/{organization_id}/scim/v2/Groups - Destructive
Update a Collaborator
Update the basic details of a collaborator. This includes the email address and name of the collaborator. Inputs include organization_id, id, userName, name, name.formatted.
PUT /organizations/{organization_id}/scim/v2/Users/{id} - Destructive
Add or Remove Previously Added Collaborators
As with the update method above, the active flag for a previously added collaborator can be set to remove or re-add them to an organization. Inputs include organization_id, id, Operations, Operations[].op, Operations[].path.
PATCH /organizations/{organization_id}/scim/v2/Users/{id} - Destructive
Remove a Collaborator
Remove a Collaborator. Inputs include organization_id, id.
DELETE /organizations/{organization_id}/scim/v2/Users/{id} - Destructive
Update Group on an Organization
The value attribute can use different formatting depending on the context. When updating a groups collaborators with the add or remove operations use an array of objects, where each objects value is an ID for a collaborator in the org: Inputs include organization_id, id, op, path, value.
PATCH /organizations/{organization_id}/scim/v2/Groups/{id} - Destructive
Delete Group on an Organization
Delete Group on an Organization. Inputs include organization_id, id.
DELETE /organizations/{organization_id}/scim/v2/Groups/{id}
build / Build
- Write
Notify of a build
Notify of a build. Inputs include apiKey, appVersion, appVersionCode, appBundleVersion, builderName.
POST /
error-reporting / Notify
- Write
Send error reports
Send error reports. Inputs include Bugsnag-Api-Key, Bugsnag-Payload-Version, Bugsnag-Sent-At, apiKey, payloadVersion.
POST /
error-reporting / Minidump
- Write
Upload minidumps
Upload minidumps. Inputs include api_key, upload_file_minidump, event.
POST /minidump
session-tracking / Session
- Write
Report a Session starting
Report the start of a session. Multiple session start events can be batched into a single request. Inputs include Bugsnag-Api-Key, Bugsnag-Payload-Version, Bugsnag-Sent-At, notifier, notifier.name.
POST /
trace / Traces
- Write
Send trace reports
Send trace reports. Inputs include Bugsnag-Api-Key, Bugsnag-Span-Sampling, Bugsnag-Integrity, Bugsnag-Sent-At, resourceSpans.
POST /traces/v1
upload / Minidumps
- Destructive
Breakpad symbol files
Upload Breakpad symbol files to allow symbolicate stacktraces within minidump files (generated when using Electron, Breakpad or Crashpad) to show human-readable stacktraces in your dashboard. If your application uses native libraries (aside from Electron and its helper libraries), you will need to generate and upload symbol files for each library and platform supported to see full stacktraces for native crashes. Inputs include api_key, overwrite, project_root, symbol_file, code_file.
POST /breakpad-symbol
upload / Dart
- Destructive
Dart symbol files
If you build your Flutter application with debug symbols stripped (--strip-debug-info) you will need to upload the generated symbol files to see the source file, line number and method in stacktraces on your dashboard. Inputs include symbolFile, apiKey, buildId, appBundleVersion, appVersion.
POST /dart-symbol
upload / Apple
- Destructive
Apple debug symbols (dSYMs)
Upload dSYM files to show human-readable function names, file paths, and line numbers in your stacktraces on iOS, macOS and other Apple platforms. Inputs include dsym, apiKey, overwrite, projectRoot.
POST /dsym
upload / Android
- Destructive
Android shared object files
For Android applications, when native code is used it will be compiled into shared object files, usually with the symbol names removed. In order to replace the obfuscated data with a human-readable stacktrace, a shared object (.so) file containing those symbols is required. This API relies on a build identifier generated by the NDK toolchain, see our docs for guidance on compatibility. Inputs include soFile, apiKey, appId, overwrite, projectRoot.
POST /ndk-symbol - Destructive
ProGuard mapping files
If you use a tool to minify and optimize your application you will need to upload a mapping file to see full debugging information in error reports including the original class and method names. Mapping files generated by ProGuard, DexGuard and R8 are supported. Inputs include proguard, apiKey, appId, versionCode, buildUUID.
POST /proguard
upload / Linux
- Destructive
Linux shared object files
Built shared object files will usually have symbol names removed. In order to replace the obfuscated data with a human-readable stacktrace, a shared object (.so) file containing those symbols is required. Inputs include soFile, apiKey, appId, overwrite, projectRoot.
POST /linux
upload / Nintendo
- Destructive
Nintendo Switch symbol files
You will need to upload the generated symbol file for your Nintendo Switch game to see the source file, line number and method in stacktraces on your dashboard. Inputs include symbolFile, apiKey, appVersion, moduleName, overwrite.
POST /nintendo-switch-symbol
upload / JavaScript
- Destructive
React Native source maps
Upload JavaScript source map files to de-obfuscate bundled code in your React Native application and show human-readable stacktraces on your dashboard. Inputs include bundle, sourceMap, apiKey, platform, appBundleVersion.
POST /react-native-source-map - Destructive
JavaScript source maps
Upload JavaScript source map files to de-obfuscate bundled code and show human-readable stacktraces on your dashboard. This is required if source maps are not publicly hosted. Inputs include sourceMap, apiKey, minifiedUrl, appVersion, minifiedFile.
POST /sourcemap
upload / Unity
- Destructive
Unity IL2CPP line number mappings
Upload the generated line mappings file (LineNumberMappings.json) for Unity apps built with IL2CPP to allow C# line numbers to be displayed for iOS and Android apps. Inputs include mappingFile, apiKey, dsymUUID, soBuildId, appId.
POST /unity-line-mappings
No operations match.
See How connections work for access and permissions, or browse all integrations.