Rollbar integration: operations for AI agents
Rollbar connects to Type.com as an integration. This page lists the 102 operations documented for Claude and Codex in Type.com: 50 read, 21 write, 31 destructive.
About Rollbar
Error tracking and monitoring platform for developers
Categories: Developer Tools & IT
How to connect Rollbar to Type.com
- Access
- Organization connection: one shared account for the workspace.
To add the connection, follow the steps in Space connections.
Documented operations
102 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.
102 operations listed.
Item
- Read
Get an item by unique ID
Get an item by project counter or occurrence UUID. Either uuid or counter must be provided. uuid must be an ocurrence UUID for an occurrence in the item. Occurrence UUIDs are part of the response in https://docs.rollbar.com/reference/create-item. counter must be an item counter for an item in the project. The counter can be found in URLs like https://rollbar.com/myaccount/myproject/items/456/ (456 is the counter).
GET /api/1/item/ - Read
List all items
Examples Get the 101st through 199th active items: curl curl -H "X-Rollbar-Access-Token: YOURACCESSTOKEN" 'https://api.rollbar.com/api/1/items/?status=active&page=2' Get the first page of items that are error or critical, in the production environment: curl curl -H "X-Rollbar-Access-Token: YOURACCESSTOKEN" 'https://api.rollbar.com/api/1/items/?level=error&level=critical&environment=production' Note that the totalcount in the result will return null if your project has more than 100,000 unique items.
GET /api/1/items - Read
Get an item (by ID)
itemid must be an item ID for an item in the project. These IDs are returned as the id field in other API calls. Note that they are NOT found in in URLs like https://rollbar.com/myaccount/myproject/items/456/ – that is the project counter.
GET /api/1/item/{itemid} - Read
List comments for an item (deprecated)
Deprecated. Use GET /item/{itemid}/events for the complete item history. Returns a paginated, chronological list of human-authored comments and resolve notes for an item. The source field distinguishes regular comments from resolve notes. Use (source, id) as the unique entry identity because IDs can overlap between sources. System-generated timeline events and comments authored by system users are not included. Project, account, and user-scoped account access tokens are supported when they have read access to the item's project. An item with no matching comments returns an empty comments array with a 200 response.
GET /api/1/item/{item_id}/comments - Read
List events for an item
Returns a paginated, chronological list of all history events for an item, including comments, status and level changes, assignments, title changes, snoozes, and merges. System-generated events and comments authored by system users are included. Snooze history is omitted when the snooze feature is unavailable for the account; explicitly requesting itemsnoozehistory in that case returns 403. Project, account, and user-scoped account access tokens are supported when they have read access to the item's project. An item with no matching events returns an empty events array with a 200 response.
GET /api/1/item/{item_id}/events - Write
Create item
Report an exception or message occurrence to a project. The event platform determines whether the token needs server-item or client-item posting scope.
POST /api/1/item/ - Write
Update an item
Used to modify an item's state. Currently supports: setting the status, level, title, assigned user when resolving, setting the "resolved in version" snoozing / unsnoozing an item (only available for paid accounts) setting the item owner to a team (only available for Advanced and Enterprise accounts) Example - curl curl -X PATCH 'https://api.rollbar.com/api/1/item/275123456' \ --header "Content-Type: application/json" \ --data '{"status": "resolved", "resolvedinversion": "aabbcc1"}'
PATCH /api/1/item/{itemid} - Write
Create a comment for an item
Creates a human-authored comment on an item. The comment is attributed to the user represented by the access token and is displayed in the item timeline with an API-origin indicator. Only a personal access token with write scope and access to the item's project is supported. Project Access Tokens and service tokens are rejected. Comment text supports the same Markdown and mention behavior as comments created in the Rollbar UI. The encoded comment and its stored metadata must fit in the existing 65,535-byte item-comment data field.
POST /api/1/item/{item_id}/comments
Occurrence
- Read
List all occurrences in a project
Returns all occurrences in the project, in pages of 20. Order is descending by occurrence ID (which is approximately descending by timestamp).
GET /api/1/instances - Read
List all occurrences in an item
Returns all occurrences of an item, in pages of 20. Order is descending by occurrence ID (which is approximately descending by timestamp).
GET /api/1/item/{item_id}/instances - Read
Get an occurrence
Returns a JSON object describing the occurrence. This is similar to the "Raw JSON" section of the occurrence detail page. instanceid must be an Occurrence ID for an occurrence in the project. These IDs are returned as the id field in other occurrence API calls, and can be found in the Rollbar UI on URLs like https://rollbar.com/Rollbar/demo/items/54/occurrences/3209095494/ (3209095494 is the Occurrence ID).
GET /api/1/instance/{instance_id} - Destructive
Delete an occurrence
Permanently deletes an occurrence. This will make it unavailable in the Rollbar UI and API. Aggregate counts are not updated. Deleting occurrences will not reduce or reset your quota. Deletion takes place asynchronously, typically within a few seconds. To verify that deletion has completed, use GET and expect a 404 response.
DELETE /api/1/instance/{instance_id}
Metrics
- Read
Get resolution time metrics for a list of projects
Get resolution time metrics for a provided list of project IDs. It can be filtered by environments, levels and frameworks.
POST /api/1/metrics/ttr - Read
Get metrics for a list of items
Get metrics for a provided list of item IDs. The endpoint follows search/query semantics as a POST request using project read access token, or account read access token with a projectid.
POST /api/1/metrics/items - Read
Occurrences over a span of time
Retrieve aggregated occurrence metrics over a time range for the authorized projects.
POST /api/1/metrics/occurrences
Service Links
- Read
GET /api/1/servicelinks
Get all Service Links
GET /api/1/service_links - Read
GET /api/1/servicelinks/{id}
Get existing Service Link by id
GET /api/1/service_links/{id} - Write
POST /api/1/servicelinks
Create Service Links
POST /api/1/service_links - Destructive
PUT /api/1/servicelinks/{id}
Replace existing Service Link
PUT /api/1/service_links/{id} - Destructive
DELETE /api/1/servicelinks/{id}
Delete existing Service Link
DELETE /api/1/service_links/{id}
Notification Channels
- Destructive
PUT /api/1/notifications/slack
Configuring Slack integration
PUT /api/1/notifications/slack - Destructive
PUT /api/1/notifications/webhook
Configuring Webhook integration
PUT /api/1/notifications/webhook - Destructive
PUT /api/1/notifications/pagerduty
Configuring PagerDuty integration
PUT /api/1/notifications/pagerduty - Destructive
PUT /api/1/notifications/email
Configuring Email Notifications integration
PUT /api/1/notifications/email
Deploy
- Read
Get a deploy
deployid must be an ID for a deploy in the project. These IDs are returned as the id field in other API calls, and can be found in the Rollbar UI on URLs like https://rollbar.com/deploy/12345/ (12345 is the Deploy ID).
GET /api/1/deploy/{deploy_id} - Read
List all deploys
Returns all deploys in the project, most recent first, in pages of 20.
GET /api/1/deploys - Write
Report a deploy
For tool-specific instructions on reporting a deploy, see our Deploy Tracking docs. For instructions on setting the default deploy timeout period, see Deploy Timeouts.
POST /api/1/deploy - Write
Update a deploy
JavaScript $.get('http://yoursite.com/test/' + id, function(data) { console.log(data); });
PATCH /api/1/deploy/{deploy_id}
Symbol Maps
- Write
Upload an iOS dSYM bundle
Note: dSYM bundles are a special type of Apple directory which are made to look like a file, because of this, all dSYM bundles must be zipped prior to upload.
POST /api/1/dsym - Write
Upload a JS source map
In the above example, our website is http://example.com, we have a minified JavaScript file at http://example.com/js/example.min.js, and we have a source tree like this: example/ example/static/js/example.min.js example/static/js/example.min.map example/static/js/site.js example/static/js/util.js
POST /api/1/sourcemap - Write
Upload an Android Proguard file
POST /api/1/proguard
POST /api/1/proguard - Write
Upload a Flutter symbols file
POST /api/1/fluttersymbols
POST /api/1/fluttersymbols
Environment
- Read
List all environments
Returns all environments in the project, in pages of 20. A successful response looks like: { 'err': 0 'result': { 'page': 1, 'environments': [ // where each environment has the shape: { 'id': 1, 'projectid': 123, 'environment': 'production', // visibility of the environment in the app (can either be 1 or 0) 'visible': 1 }, ... ] } }
GET /api/1/environments
RQL
- Read
Check an RQL job
Response The response will be a RQL Job resource, example: json { "err" 0, "result": { "id": 123, // job id "projectid": 456, "querystring": "show tables", "status": "new", // One of "new", "running", "success", "failed", "cancelled", or "timedout" "jobhash": "abcdefabcdefabcdef", "datecreated": 1446598885, "datemodified": 1446598885, "result": {...} // A RQL job resource if expand=result is used in query string } }
GET /api/1/rql/job/{job_id} - Read
List all RQL jobs
If you use a project access token or an account token with projectid in the request, all rql jobs for that project will be returned. If you use an account access token without a projectid, all rql jobs for the account will be returned. Response json { "err" 0, "result": [ { ... }, // RQL job resource ... ] }
GET /api/1/rql/jobs/ - Read
Get RQL job results
Response The response will be a RQL job result resource, example: json { "err" 0, "result": { "jobid": 123, // job id "result": { "rows": [{...}], "selectionColumns": [...], "columns": [...], "errors": [], "warnings": [], "rowcount": 1, "executionTime": 123 }, "job": {...} // A RQL job resource if expand=job is set in the query string } }
GET /api/1/rql/job/{job_id}/result - Write
Create an RQL job
Response The response will be a RQL Job resource, example: json { "err" 0, "result": { "id": 123, // job id "projectid": 456, "querystring": "show tables", "status": "new", // One of "new", "running", "success", "failed", "cancelled", or "timedout" "jobhash": "abcdefabcdefabcdef", "datecreated": 1446598885, "datemodified": 1446598885 } }
POST /api/1/rql/jobs/ - Destructive
Cancel an RQL job
Response The response will be a RQL Job resource, example: json { "err" 0, "result": { "id": 123, // job id "projectid": 456, "querystring": "show tables", "status": "cancelled", // One of "new", "running", "success", "failed", "cancelled", or "timedout" "jobhash": "abcdefabcdefabcdef", "datecreated": 1446598885, "datemodified": 1446598885 } }
POST /api/1/rql/job/{job_id}/cancel
Teams
- Read
List all teams
GET /api/1/teams
GET /api/1/teams - Read
Get a team
GET /api/1/team/{team_id}
GET /api/1/team/{team_id} - Write
Create a team
Access Levels standard is the only access level you can choose in the UI. light and view are API-only team access levels. light gives the team read and write access, but not to all settings. view gives the team read-only access.
POST /api/1/teams - Destructive
Delete a team
DELETE /api/1/team/{team_id}
DELETE /api/1/team/{team_id}
Reports
- Read
Get top active items
List the most active items for the requested time interval and metric.
GET /api/1/reports/top_active_items - Read
Get active occurrence counts
Analogous to "Hourly Error/Critical Occurrences" and "Daily Error/Critical Occurrences" on the Project Dashboard. Returns an array of recent counts as [timestamp, count] pairs, where each count is the number of matching active occurrences in the time range [timestamp, timestamp + bucketsize - 1]. Timestamps are UNIX timestamps, in whole seconds. Response json { "err": 0, "result": [ [ // timestamp 1728561200, // count (number of occurrences from time 1728561200 until time 1728564799) 0 ], [ 1728564800, 0 ], [ 1728568400, 0 ], [ 1728572000, 6 ] ] }
GET /api/1/reports/occurrence_counts - Read
Get activated item counts
Analogous to "Daily New/Reactivated Items" graph on the Project Dashboard. Returns an array of recent counts as [timestamp, count] pairs, where each count is the number of items that were first seen or reactivated in the time range [timestamp, timestamp + bucketsize - 1]. Timestamps are UNIX timestamps, in whole seconds. Response json { "err": 0, "result": [ [ // timestamp 1728561200, // count (number of occurrences from time 1728561200 until time 1728564799) 0 ], [ 1728564800, 0 ], [ 1728568400, 0 ], [ 1728572000, 6 ] ] }
GET /api/1/reports/activated_counts
Projects
- Read
List all projects
GET /api/1/projects
GET /api/1/projects - Read
Get a project
GET /api/1/project/{project_id}
GET /api/1/project/{project_id} - Write
Create a project
POST /api/1/projects
POST /api/1/projects - Destructive
Delete a project
DELETE /api/1/project/{project_id}
DELETE /api/1/project/{project_id}
Project Access Tokens
- Read
List all project access tokens
GET /api/1/project/{project_id}/access_tokens
GET /api/1/project/{project_id}/access_tokens - Write
Create a project access token
POST /api/1/project/{project_id}/access_tokens
POST /api/1/project/{project_id}/access_tokens - Write
Update a rate limit (token identifier in the path)
To update the rate limit, include either the legacy access token or the secure public ID in the tokenidentifier field of the URL.
PATCH /api/1/project/{project_id}/access_token/{token_identifier} - Write
Update a rate limit (token identifier in the body)
To update a rate limit for a project access token, provide either the projectaccesstoken value or the token’s publicid in the body parameters.
PATCH /api/1/project/{project_id}/access_token - Destructive
Delete a project access token (token identifier in the path)
To delete a project access token, include either the legacy access token or the secure public ID in the tokenidentifier field of the URL.
DELETE /api/1/project/{project_id}/access_token/{token_identifier} - Destructive
Delete a project access token (token identifier in the body)
To delete a project access token, provide either the projectaccesstoken value or the token’s publicid in the body parameters.
DELETE /api/1/project/{project_id}/access_token
Users
- Read
List all users
List all users who are members of an account Response Format json { "err": 0, "result": { "users": [ { "username": "brianr", "id": 1, "email": "brian@rollbar.com" }, { "username": "coryvirok", "id": 2, "email": "cory@rollbar.com" } ] } }
GET /api/1/users - Read
Get a user
Get user details for a given account Returns basic information about the user, as relevant to the account your access token is for. This is the same information available on the "Members" page in the Rollbar UI. Sample Response json { "err": 0, "result": { "id": 14, "username": "brian", "email": "brian@rollbar.com", "emailenabled": 1 } }
GET /api/1/user/{user_id}
Teams ⟷ Users
- Read
List a team's users
GET /api/1/team/{team_id}/users
GET /api/1/team/{team_id}/users - Read
Check if a user is assigned to a team
GET /api/1/team/{team_id}/user/{user_id}
GET /api/1/team/{team_id}/user/{user_id} - Read
List a user's teams
GET /api/1/user/{user_id}/teams
GET /api/1/user/{user_id}/teams - Read
List invitations to a team
Returns all invites ever sent for the team–pending, accepted, rejected, and canceled. Example response { "err": 0, "result": [ { "id": 71328, "fromuserid": 5325, "teamid": 272686, "toemail": "gilfoyle@pidepiper.com", "status": "pending", "datecreated": 1519946545, "dateredeemed": null } ] }
GET /api/1/team/{team_id}/invites - Read
Get invitation
Example Response json { "err": 0, "result": { "id": 71328, "fromuserid": 5325, "teamid": 272686, "toemail": "gilfoyle@piedpiper.com", "status": "pending", "datecreated": 1519946545, "dateredeemed": null } }
GET /api/1/invite/{invite_id} - Write
Invite an email address to a team
Invites a user to the specific team, using the user's email address. If the email address belongs to an existing Rollbar user, they will be immediately added to the team, and sent an email notification. Otherwise, an invite email will be sent, containing a signup link that will allow the recipient to join the specified team. Example Response { "err": 0, "result": { "id": 71328, "fromuserid": 5325, "teamid": 272686, "toemail": "gilfoyle@piedpiper.com", "status": "pending", "datecreated": 1519946545, "dateredeemed": null } }
POST /api/1/team/{team_id}/invites - Destructive
Assign a user to team
PUT /api/1/team/{team_id}/user/{user_id}
PUT /api/1/team/{team_id}/user/{user_id} - Destructive
Remove a user from a team
DELETE /api/1/team/{team_id}/user/{user_id}
DELETE /api/1/team/{team_id}/user/{user_id} - Destructive
Cancel invitation
Returns a 200 if the invitation was successfully canceled.
DELETE /api/1/invite/{invite_id}
Teams ⟷ Projects
- Read
Check if a team is assigned to a project
Returns 200 if the team is assigned to a project, 404 if the team is not assigned to the project. Example responses json { "err": 0, "result": { "teamid": 272686, "projectid": 165090 } } json { "err": 1, "message": "Project is not in this Team." }
GET /api/1/team/{team_id}/project/{project_id} - Read
List a team's projects
Example Response json { "err": 0, "result": [ { "teamid": 272686, "projectid": 178029 }, { "teamid": 272686, "projectid": 178030 } ] }
GET /api/1/team/{team_id}/projects - Read
List a project's teams
Example Response json { "err": 0, "result": [ { "teamid": 272686, "projectid": 178029 }, { "teamid": 272687, "projectid": 178029 } ] }
GET /api/1/project/{project_id}/teams - Destructive
Assign a team to a project
Example Response json { "err": 0, "result": { "teamid": 272686, "projectid": 165090 } }
PUT /api/1/team/{team_id}/project/{project_id} - Destructive
Remove a team from a project
DELETE /api/1/team/{team_id}/project/{project_id}
DELETE /api/1/team/{team_id}/project/{project_id}
Users ⟷ Projects
- Read
List a user's projects
Example response: json { "err": 0, "result": { "projects": [ { "status": 1, "slug": "mox", "id": 1, "accountid": 61 }, { "status": 1, "slug": "moxrts", "id": 25, "accountid": 61 } ] } }
GET /api/1/user/{user_id}/projects
People
- Read
Get person deletion status
Check on the status of a person deletion request. The response will include a status, e.g. { "err": 0, "result": { "state": "success", // possible values are "new","running","paused","success","cancelled","failed" "id": 3 } }
GET /api/1/people/delete_jobs/{job_id} - Destructive
Request person deletion
This endpoint allows for removal of a tracked person from all projects within an account. To identify the person, you must provide exactly one of the following: email username personid These correspond to the values transmitted in the original occurrences (see the docs for Create item) and can also be found by viewing any tracked person via the People Tracking page in any project. Requests for person deletion are asynchronous. The returned value will include an id property that can be used to check the status of the deletion process, e.g. { "err": 0, "result": { "id": 3 } }
POST /api/1/people/delete_jobs/
Slack Notification Rules
- Read
GET /api/1/notifications/slack/rules
Get all Slack rules
GET /api/1/notifications/slack/rules - Read
GET /api/1/notifications/slack/rule/{ruleid}
Get a notification rule by ID
GET /api/1/notifications/slack/rule/{rule_id} - Write
POST /api/1/notifications/slack/rules
Create Slack notification rules
POST /api/1/notifications/slack/rules - Destructive
Replace existing notification rules
This endpoint replaces all existing rules for the channel with the ones provided. To update a specific rule, use the /api/1/notifications/slack/rule/{ruleid} endpoint instead. To add new rules, use the POST endpoint.
PUT /api/1/notifications/slack/rules - Destructive
PUT /api/1/notifications/slack/rule/{ruleid}
Update a notification rule by ID
PUT /api/1/notifications/slack/rule/{rule_id} - Destructive
DELETE /api/1/notifications/slack/rule/{ruleid}
Delete a notification rule by ID
DELETE /api/1/notifications/slack/rule/{rule_id}
Pager Duty Notification Rules
- Read
GET /api/1/notifications/pagerduty/rules
Get all PagerDuty notification rules
GET /api/1/notifications/pagerduty/rules - Read
GET /api/1/notifications/pagerduty/rule/{ruleid}
Get a notification rule by ID
GET /api/1/notifications/pagerduty/rule/{rule_id} - Write
POST /api/1/notifications/pagerduty
Create PagerDuty notification rules
POST /api/1/notifications/pagerduty - Destructive
Replace existing notification rules
This endpoint replaces all existing rules for the channel with the ones provided. To update a specific rule, use the /api/1/notifications/slack/rule/{ruleid} endpoint instead. To add new rules, use the POST endpoint.
PUT /api/1/notifications/pagerduty/rules - Destructive
PUT /api/1/notifications/pagerduty/rule/{ruleid}
Update a notification rule by ID
PUT /api/1/notifications/pagerduty/rule/{rule_id} - Destructive
DELETE /api/1/notifications/pagerduty/rule/{ruleid}
Delete a notification rule by ID
DELETE /api/1/notifications/pagerduty/rule/{rule_id}
Email Notification Rules
- Read
GET /api/1/notifications/email/rules
Get all email notification rules
GET /api/1/notifications/email/rules - Read
GET /api/1/notifications/email/rule/{ruleid}
Get a notification rule by ID
GET /api/1/notifications/email/rule/{rule_id} - Write
POST /api/1/notifications/email/rules
Create Email notification rules
POST /api/1/notifications/email/rules - Destructive
Replace existing notification rules
This endpoint replaces all existing rules for the channel with the ones provided. To update a specific rule, use the /api/1/notifications/slack/rule/{ruleid} endpoint instead. To add new rules, use the POST endpoint.
PUT /api/1/notifications/email/rules - Destructive
PUT /api/1/notifications/email/rule/{ruleid}
Update a notification rule by ID
PUT /api/1/notifications/email/rule/{rule_id} - Destructive
DELETE /api/1/notifications/email/rule/{ruleid}
Delete a notification rule by ID
DELETE /api/1/notifications/email/rule/{rule_id}
Webhook Notification Rules
- Read
GET /api/1/notifications/webhook/rules
Get all Webhook rules
GET /api/1/notifications/webhook/rules - Read
GET /api/1/notifications/webhook/rule/{ruleid}
Get a notification rule by ID
GET /api/1/notifications/webhook/rule/{rule_id} - Write
POST /api/1/notifications/webhook/rules
Create Webhook notification rules
POST /api/1/notifications/webhook/rules - Destructive
Replace existing notification rules
This endpoint replaces all existing rules for the channel with the ones provided. To update a specific rule, use the /api/1/notifications/webhook/rule/{ruleid} endpoint instead. To add new rules, use the POST endpoint.
PUT /api/1/notifications/webhook/rules - Destructive
PUT /api/1/notifications/webhook/rule/{ruleid}
Update a notification rule by ID
PUT /api/1/notifications/webhook/rule/{rule_id} - Destructive
DELETE /api/1/notifications/webhook/rule/{ruleid}
Delete a notification rule by ID
DELETE /api/1/notifications/webhook/rule/{rule_id}
Replay
- Read
Get a session replay
Retrieves the replay payload for a recorded session in the specified environment. Requires a project access token with read scope, or account access token with read scope and a projectid.
GET /api/1/environment/{environment}/session/{sessionId}/replay/{replayId} - Destructive
Delete a session replay
Deletes a replay for a recorded session in the specified environment. Requires a project access token with write scope.
DELETE /api/1/environment/{environment}/session/{sessionId}/replay/{replayId}
Versions
- Read
Code version details in one project
Returns the details about one specific code version in one project https://docs.rollbar.com/docs/versions
GET /api/1/versions/{version} - Read
List items by code version
List items that have occurrences for one specific code version. https://docs.rollbar.com/docs/versions
GET /api/1/versions/{version}/items
No operations match.
See How connections work for access and permissions, or browse all integrations.