Rollbar

Delete a session replay via DELETE /api/1/environment/{environment}/session/{sessionId}/replay/{replayId}. Deletes a replay for a recorded session in the specified environment. Requires a project access token with `write` scope. DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Delete an occurrence via DELETE /api/1/instance/{instance_id}. 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. DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Cancel invitation via DELETE /api/1/invite/{invite_id}. Returns a `200` if the invitation was successfully canceled. DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Delete an email notification rule via DELETE /api/1/notifications/email/rule/{rule_id}. Delete a notification rule by ID DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Delete a PagerDuty notification rule via DELETE /api/1/notifications/pagerduty/rule/{rule_id}. Delete a notification rule by ID DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Delete a Slack notification rule via DELETE /api/1/notifications/slack/rule/{rule_id}. Delete a notification rule by ID DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Delete a webhook notification rule via DELETE /api/1/notifications/webhook/rule/{rule_id}. Delete a notification rule by ID DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Delete a project via DELETE /api/1/project/{project_id}. DESTRUCTIVE: delete a project. The project's items, occurrences, deploys and access tokens go with it, and Rollbar offers no undo and no recycle bin through this API. Any client still reporting to one of that project's tokens stops being recorded. DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Delete a project access token (token identifier in the body) via DELETE /api/1/project/{project_id}/access_token. DESTRUCTIVE: delete a project access token, naming it in the request BODY rather than in the path. Send `public_id` -- the non-secret handle `List all project access tokens` returns for every token -- which is the form to prefer. `project_access_token` is accepted as an alternative and takes the token's own VALUE, which means putting a live credential into this tool's arguments, where it reaches the model's context and the audit record; use it only when you hold a token value whose public id you cannot look up, which is the case Rollbar's token list cannot answer because it does not return values. Deleting a token cannot be undone and any client still authenticating with it starts failing immediately. The sibling tool `Delete a project access token` addresses the same token by its public id in the URL and carries no body. DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Delete a project access token (token identifier in the path) via DELETE /api/1/project/{project_id}/access_token/{token_identifier}. To delete a project access token, include either the legacy access token or the secure public ID in the token_identifier field of the URL. DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Delete a service link via DELETE /api/1/service_links/{id}. Delete existing Service Link DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Delete a team via DELETE /api/1/team/{team_id}. DESTRUCTIVE: delete a team. Its user assignments and project assignments go with it, and members lose whatever access the team granted them. The users and the projects themselves are untouched. DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Remove a team from a project via DELETE /api/1/team/{team_id}/project/{project_id}. Unassign a team from a project. Members of that team lose the access it gave them in that project; neither the team nor the project is deleted, and the assign tool restores the link exactly. DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Remove a user from a team via DELETE /api/1/team/{team_id}/user/{user_id}. Remove a user from a team. They lose the access that team gave them in its projects; their Rollbar account and their other teams are untouched. Re-adding them with the assign tool restores it exactly. DESTRUCTIVE: the resource is removed and there is no undo through this API. Read it first with the matching Get or List tool if you may need what it held.

Get a deploy via GET /api/1/deploy/{deploy_id}. `deploy_id` 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).

List all deploys via GET /api/1/deploys. Returns all deploys in the project, most recent first, in pages of 20.

Get a session replay via GET /api/1/environment/{environment}/session/{sessionId}/replay/{replayId}. 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 `project_id`.

List all environments via GET /api/1/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, 'project_id': 123, 'environment': 'production', // visibility of the environment in the app (can either be 1 or 0) 'visible': 1 }, ... ] } } ```

Get an occurrence via GET /api/1/instance/{instance_id}. Returns a JSON object describing the occurrence. This is similar to the "Raw JSON" section of the occurrence detail page. `instance_id` 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).

List all occurrences in a project via GET /api/1/instances. Returns all occurrences in the project, in pages of 20. Order is descending by occurrence ID (which is approximately descending by timestamp).

Get invitation via GET /api/1/invite/{invite_id}. # Example Response ```json { "err": 0, "result": { "id": 71328, "from_user_id": 5325, "team_id": 272686, "to_email": "gilfoyle@piedpiper.com", "status": "pending", "date_created": 1519946545, "date_redeemed": null } } ```

Get an item by unique ID via GET /api/1/item. 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 an item (by project counter) via GET /api/1/item_by_counter/{counter}. `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). The success response is a 301 redirect like this: ``` HTTP/1.1 301 Moved Permanently Location: /api/1/item/272505123 { "err": 0, "result": { "itemId": 272505123, "path": "/api/1/item/272505123", "uri": "/api/1/item/272505123" } } ``` NEEDS A PROJECT ACCESS TOKEN: an ACCOUNT access token is refused on this route no matter what scopes it holds and no matter whether `project_id` is supplied (measured 2026-09-24). Connect a Rollbar connection holding a PROJECT access token with `read` and `write`, minted at the project's Settings -> Project Access Tokens. That token in turn cannot reach the account-level tools -- projects, teams, users, invites -- so the two are different connections rather than one better token.

List comments for an item via GET /api/1/item/{item_id}/comments. Deprecated. Use `GET /item/{item_id}/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.

List events for an item via GET /api/1/item/{item_id}/events. 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 `item_snooze_history` 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.

List all occurrences in an item via GET /api/1/item/{item_id}/instances. Returns all occurrences of an item, in pages of 20. Order is descending by occurrence ID (which is approximately descending by timestamp).

Get an item (by ID) via GET /api/1/item/{itemid}. `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.

List all items via GET /api/1/items. List items -- Rollbar's deduplicated error groups -- for one project, newest activity first and 100 to a page. Narrow with `status` (active, resolved, muted, archived), `level` (debug through critical, repeatable to union several), `environment`, `framework`, `query` for a title substring, and `assigned_user_id` or `owner_user_id`. `page` walks the pages. A result's `total_count` is null once a project holds more than 100,000 unique items, which is Rollbar declining to count rather than an empty result. THIS TOOL NEEDS A PROJECT ACCESS TOKEN: measured 2026-09-24, an account token answers 422 'Internal Server Error' here bare, with `project_id`, with a filter and with a trailing slash alike, while a project token answers 200. NEEDS A PROJECT ACCESS TOKEN: an ACCOUNT access token is refused on this route no matter what scopes it holds and no matter whether `project_id` is supplied (measured 2026-09-24). Connect a Rollbar connection holding a PROJECT access token with `read` and `write`, minted at the project's Settings -> Project Access Tokens. That token in turn cannot reach the account-level tools -- projects, teams, users, invites -- so the two are different connections rather than one better token.

Get an email notification rule via GET /api/1/notifications/email/rule/{rule_id}. Get a notification rule by ID

List email notification rules via GET /api/1/notifications/email/rules. Get all email notification rules

Get a PagerDuty notification rule via GET /api/1/notifications/pagerduty/rule/{rule_id}. Get a notification rule by ID

List PagerDuty notification rules via GET /api/1/notifications/pagerduty/rules. Get all PagerDuty notification rules

Get a Slack notification rule via GET /api/1/notifications/slack/rule/{rule_id}. Get a notification rule by ID

List Slack notification rules via GET /api/1/notifications/slack/rules. Get all Slack rules

Get a webhook notification rule via GET /api/1/notifications/webhook/rule/{rule_id}. Get a notification rule by ID

List webhook notification rules via GET /api/1/notifications/webhook/rules. Get all Webhook rules

Get person deletion status via GET /api/1/people/delete_jobs/{job_id}. 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 a project via GET /api/1/project/{project_id}. Retrieve one project by id, with its name, status, account id, timestamps and `settings_data` -- the project's timezone, time format, grouping configuration and per-service integration settings.

List all project access tokens via GET /api/1/project/{project_id}/access_tokens. List the access tokens minted on one project, each with its name, scopes, status, rate-limit window and `public_id`. THE TOKEN VALUES ARE NOT RETURNED: Rollbar encrypts tokens created since April 2025 and shows a token's value only at the moment it is created, which this integration also redacts. Use this to audit which scopes exist on a project, not to recover a token. THE TOKEN VALUE IS REDACTED FROM THIS RESULT. Rollbar returns the `access_token` field as a live credential, and Agentic Fabriq replaces it before the reply leaves the connector, because a tool result reaches the model's context and the audit pipeline. Everything else -- the `public_id`, the scopes, the status, the rate-limit window -- is returned untouched. Rollbar shows a token's value only once, at creation, and encrypts it afterwards, so if you need the value itself, mint the token in the Rollbar dashboard where it is displayed.

List a project's teams via GET /api/1/project/{project_id}/teams. # Example Response ```json { "err": 0, "result": [ { "team_id": 272686, "project_id": 178029 }, { "team_id": 272687, "project_id": 178029 } ] } ```

List all projects via GET /api/1/projects. List every project on the account, each with its id, name, status, timezone and grouping settings. This is how a caller DISCOVERS the `project_id` that most other operations take as a path segment or a query parameter, and it is the operation an account access token exists for. Rollbar has no per-account host, so nothing about the connection has to be configured to reach it.

Get activated item counts via GET /api/1/reports/activated_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 + bucket_size - 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 active occurrence counts via GET /api/1/reports/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 + bucket_size - 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 top active items via GET /api/1/reports/top_active_items. # Response ```json { "err": 0, "result": [ // each element in the list is an object with an "item" object and a "counts" list { // data describing the item (similar to that returned by GET /api/1/item/:id) "item": { "id": 2071, "counter": 1007, "environment": "production", "framework": 0, "last_occurrence_timestamp": 1728410581, "level": 40, "occurrences": 54, "project_id": 12345, "title": "Something went wrong", "unique_occurrences": 5 }, // list of occurrence counts in the past 24 hours. Oldest first. "counts": [12, 10, 7, 3, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 8, 5, 6] }, { /* more elements ... */ } ] } ``` By default, the sort of the top items is by the level of severity, then the number of occurrences. E.g. an item with a `warning` level and 300 occurrences will be below an item with an `error` level and 150 occurrences. This behavior can be changed by passing `sort=occurrences` in the query parameters, which will sort only by the number of occurrences in the time period. Note that the level and framework are returned as integers here. `10`, `20`, `30`, `40`, and `50` representing the `debug`, `info`, `warning`, `error`, and `critical` levels, respectively. For the full integer-framework mapping, please see the [Framework IDs](https://docs.rollbar.com/docs/rql#framework-ids) section in our docs.

Check an RQL job via GET /api/1/rql/job/{job_id}. # Response The response will be a RQL Job resource, example: ```json { "err" 0, "result": { "id": 123, // job id "project_id": 456, "query_string": "show tables", "status": "new", // One of "new", "running", "success", "failed", "cancelled", or "timed_out" "job_hash": "abcdefabcdefabcdef", "date_created": 1446598885, "date_modified": 1446598885, "result": {...} // A RQL job resource if expand=result is used in query string } }``

Get RQL job results via GET /api/1/rql/job/{job_id}/result. # Response The response will be a RQL job result resource, example: ```json { "err" 0, "result": { "job_id": 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 } }```

List all RQL jobs via GET /api/1/rql/jobs. If you use a project access token or an account token with `project_id` in the request, all rql jobs for that project will be returned. If you use an account access token without a `project_id`, all rql jobs for the account will be returned. # Response ```json { "err" 0, "result": [ { ... }, // RQL job resource ... ] } ```

List service links via GET /api/1/service_links. Get all Service Links

Get a service link via GET /api/1/service_links/{id}. Get existing Service Link by id

Get a team via GET /api/1/team/{team_id}. Retrieve one team by id, with its name and access level -- `standard`, `light`, `view` or `everyone`, which is what the team's members may do in the projects it is assigned to.

List invitations to a team via GET /api/1/team/{team_id}/invites. Returns all invites ever sent for the team–pending, accepted, rejected, and canceled. # Example response ``` { "err": 0, "result": [ { "id": 71328, "from_user_id": 5325, "team_id": 272686, "to_email": "gilfoyle@pidepiper.com", "status": "pending", "date_created": 1519946545, "date_redeemed": null } ] } ```

Check if a team is assigned to a project via GET /api/1/team/{team_id}/project/{project_id}. 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": { "team_id": 272686, "project_id": 165090 } } ``` ```json { "err": 1, "message": "Project is not in this Team." } ```

List a team's projects via GET /api/1/team/{team_id}/projects. # Example Response ```json { "err": 0, "result": [ { "team_id": 272686, "project_id": 178029 }, { "team_id": 272686, "project_id": 178030 } ] } ```

Check if a user is assigned to a team via GET /api/1/team/{team_id}/user/{user_id}. Ask whether one user is assigned to one team. A 200 carrying the `team_id`/`user_id` pair means yes. Membership is a STATUS question, so read the reply rather than inferring it from an error: this answers 404 when the user is not on the team and 403 when the credential cannot see the team at all, and those are different facts.

List a team's users via GET /api/1/team/{team_id}/users. List the users assigned to one team, one page at a time with `page`. This is the team's membership, not the account's user list.

List all teams via GET /api/1/teams. List the teams on the account, each with its id, name and access level. A team is what Rollbar assigns users and projects to.

Get a user via GET /api/1/user/{user_id}. Get one user on the account by id -- username, email and whether email notifications are enabled -- which is the same record the Members page in the Rollbar dashboard shows. `List all users` returns the ids, and the reply describes the user only as far as this account's own membership goes.

List a user's projects via GET /api/1/user/{user_id}/projects. # Example response: ```json { "err": 0, "result": { "projects": [ { "status": 1, "slug": "mox", "id": 1, "account_id": 61 }, { "status": 1, "slug": "moxrts", "id": 25, "account_id": 61 } ] } }```

List a user's teams via GET /api/1/user/{user_id}/teams. List the teams one user belongs to, as a `teams` array. The inverse of listing a team's users, and the cheaper question when the subject is the person rather than the team.

List all users via GET /api/1/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" } ] } } ```

Code version details in one project via GET /api/1/versions/{version}. Returns the details about one specific code version in one project https://docs.rollbar.com/docs/versions

List items by code version via GET /api/1/versions/{version}/items. List items that have occurrences for one specific code version. https://docs.rollbar.com/docs/versions

Update a deploy via PATCH /api/1/deploy/{deploy_id}. ```JavaScript $.get('http://yoursite.com/test/' + id, function(data) { console.log(data); });``` DIFFERENT TOKEN FAMILY: this is one of only three tools that need a PROJECT access token minted with the `post_server_item` scope (Rollbar dashboard -> the project -> Settings -> Project Access Tokens). An ACCOUNT token -- the one that reaches most of this integration -- is not recognised on this route at all and answers 403 'access token not found', a project `read`+`write` token answers 403 'post_server_item scope is required', and Rollbar REFUSES to mint a token holding `post_server_item` alongside `read` or `write` (400 'Invalid scope combination', measured 2026-09-24). So a connection that can call this tool is a SEPARATE connection that can call almost nothing else; that is Rollbar's rule, not Agentic Fabriq's.

Update an item via PATCH /api/1/item/{itemid}. 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", "resolved_in_version": "aabbcc1"}' ``` NEEDS A PROJECT ACCESS TOKEN: an ACCOUNT access token is refused on this route no matter what scopes it holds and no matter whether `project_id` is supplied (measured 2026-09-24). Connect a Rollbar connection holding a PROJECT access token with `read` and `write`, minted at the project's Settings -> Project Access Tokens. That token in turn cannot reach the account-level tools -- projects, teams, users, invites -- so the two are different connections rather than one better token.

Update a rate limit (token identifier in the body) via PATCH /api/1/project/{project_id}/access_token. To update a rate limit for a project access token, provide either the project_access_token value or the token’s public_id in the body parameters. PLAN-GATED: configuring token rate limits needs a paid Rollbar plan. Measured 2026-09-24 on a free account: 422 'Upgrade account to configure rate limits'. That is an entitlement rather than a credential fault -- the token is fine, and re-pasting it changes nothing.

Update a rate limit (token identifier in the path) via PATCH /api/1/project/{project_id}/access_token/{token_identifier}. To update the rate limit, include either the legacy access token or the secure public ID in the token_identifier field of the URL. PLAN-GATED: configuring token rate limits needs a paid Rollbar plan. Measured 2026-09-24 on a free account: 422 'Upgrade account to configure rate limits'. That is an entitlement rather than a credential fault -- the token is fine, and re-pasting it changes nothing.

Report a deploy via POST /api/1/deploy. For tool-specific instructions on reporting a deploy, see our [Deploy Tracking](doc:deploy-tracking) docs. For instructions on setting the default deploy timeout period, see [Deploy Timeouts](https://docs.rollbar.com/docs/deploy-tracking#section-deploy-timeout). DIFFERENT TOKEN FAMILY: this is one of only three tools that need a PROJECT access token minted with the `post_server_item` scope (Rollbar dashboard -> the project -> Settings -> Project Access Tokens). An ACCOUNT token -- the one that reaches most of this integration -- is not recognised on this route at all and answers 403 'access token not found', a project `read`+`write` token answers 403 'post_server_item scope is required', and Rollbar REFUSES to mint a token holding `post_server_item` alongside `read` or `write` (400 'Invalid scope combination', measured 2026-09-24). So a connection that can call this tool is a SEPARATE connection that can call almost nothing else; that is Rollbar's rule, not Agentic Fabriq's.

Create item via POST /api/1/item. Rollbar receives Occurrences (exceptions and messages) via a RESTful JSON API. Clients send JSON data via an HTTP POST to https://api.rollbar.com/api/1/item/ We strongly recommend using HTTPS, but HTTP is also supported. For HTTP, use http://api.rollbar.com/api/1/item/ POSTed JSON data is accepted either as the body of the request, or form-encoded as the value of the payload parameter (which should be the only parameter). All responses (including error responses) are returned as JSON. ### Data Format The example JSON payload below describes all the required and optional params that Rollbar understands. The meaning of each key is explained in the comments. ```json { // Required: data "data": { // Required: environment // The name of the environment in which this occurrence was seen. // A string up to 255 characters. For best results, use "production" or "prod" for your // production environment. // You don't need to configure anything in the Rollbar UI for new environment names; // we'll detect them automatically. "environment": "production", // Required: body // The main data being sent. It can either be a message, an exception, or a crash report. "body": { // Required: "trace", "trace_chain", "message", or "crash_report" (exactly one) // If this payload is a single exception, use "trace" // If a chain of exceptions (for languages that support inner exceptions), use "trace_chain" // If a message with no stack trace, use "message" // If an iOS crash report, use "crash_report" // Optional: "telemetry". Only applicable if you are sending telemetry data. "telemetry": [ { // Required: level // The severity level of the telemetry data. One of: "critical", "error", "warning", "info", "debug". "level": "info", // Required: type // The type of telemetry data. One of: "log", "network", "dom", "navigation", "error", "manual". "type": "network", // Required: source // The source of the telemetry data. Usually "client" or "server". "source": "client", // Required: timestamp_ms // When this occurred, as a unix timestamp in milliseconds. "timestamp_ms": 1720413393557, // Required: body // The key-value pairs for the telemetry data point. See "body" key below. // If type above is "log", body should contain "message" key. // If type above is "network", body should contain "method", "url", and "status_code" keys. // If type above is "dom", body should contain "element" key. // If type above is "navigation", body should contain "from" and "to" keys. // If type above is "error", body should contain "message" key. "body": { "subtype": "xhr", "method": "GET", "url": "/api/1/item/4/", "status_code": "200", "start_timestamp_ms": 1720413394557, "end_timestamp_ms": 1720413394957 }, }, // more telemetry array elements follow... ], // Option 1: "trace" "trace": { // Required: frames // A list of stack frames, ordered such that the most recent call is last in the list. "frames": [ // Each frame is an object. { // Required: filename // The filename including its full path. "filename": "/Users/brian/www/mox/mox/views/project.py", // Optional: lineno // The line number as an integer "lineno": 26, // Optional: colno // The column number as an integer "colno": 8, // Optional: method // The method or function name "method": "index", // Optional: code // The line of code "code": "_save_last_project(request, project_id, force=True)", // Optional: class_name // A string containing the class name. // Used in the UI when the payload's top-level "language" key has the value "java" "class_name": "java.lang.String", // Optional: context // Additional code before and after the "code" line "context": { // Optional: pre // List of lines of code before the "code" line "pre": [ "project = request.context", "project_id = project.id" ], // Optional: post // List of lines of code after the "code" line "post": [] }, // (Deprecated) Optional: args // List of values of positional arguments to the method/function call // NOTE: as this can contain sensitive data, you may want to scrub the values "args": ["<Request object>", 25], // (Deprecated) Optional: kwargs // Object of keyword arguments (name => value) to the method/function call // NOTE: as this can contain sensitive data, you may want to scrub the values "kwargs": { "force": true }, // Optional: argspec // List of the names of the arguments to the method/function call. "argspec": ["request", "user"], // Optional: varargspec // If the function call takes an arbitrary number of unnamed positional arguments, // the name of the argument that is the list containing those arguments. // For example, in Python, this would typically be "args" when "*args" is used. // The actual list will be found in locals. "varargspec": "args", // Optional: keywordspec // If the function call takes an arbitrary number of keyword arguments, the name // of the argument that is the object containing those arguments. // For example, in Python, this would typically be "kwargs" when "**kwargs" is used. // The actual object will be found in locals. "keywordspec": "kwargs", // Optional: locals // Object of local variables for the method/function call. // The values of variables from argspec, vararspec and keywordspec // can be found in locals. "locals": { "request": "<Request object>", "user": "<User object>", "args": [true, "Python"], "kwargs": {"level": "warning"} } }, { "filename": "/Users/brian/www/mox/mox/views/project.py", "lineno": 497, "method": "_save_last_project", "code": "user = foo" } ], // Required: exception // An object describing the exception instance. "exception": { // Required: class // The exception class name. "class": "NameError", // Optional: message // The exception message, as a string "message": "global name 'foo' is not defined", // Optional: description // An alternate human-readable string describing the exception // Usually the original exception message will have been machine-generated; // you can use this to send something custom "description": "Something went wrong while trying to save the user object" } }, // Option 2: "trace_chain" // Used for exceptions with inner exceptions or causes "trace_chain": [ // Each element in the list should be a "trace" object, as shown above // Must contain at least one element. ], // Option 3: "message" // Only one of "trace", "trace_chain", "message", or "crash_report" should be present. // Presence of a "message" key means that this payload is a log message. "message": { // Required: body // The primary message text, as a string "body": "Request over threshold of 10 seconds", // Can also contain any arbitrary keys of metadata. Their values can be any valid JSON. // For example: "route": "home#index", "time_elapsed": 15.23 }, // Option 4: "crash_report" // Only one of "trace", "trace_chain", "message", or "crash_report" should be present. "crash_report": { // Required: raw // The raw crash report, as a string // Rollbar expects the format generated by rollbar-ios "raw": "<crash report here>" } }, // Optional: level // The severity level. One of: "critical", "error", "warning", "info", "debug" // Defaults to "error" for exceptions and "info" for messages. // The level of the *first* occurrence of an item is used as the item's level. "level": "error", // Optional: timestamp // When this occurred, as a unix timestamp. "timestamp": 1723188822, // Optional: code_version // A string, up to 40 characters, describing the version of the application code // Rollbar understands these formats: // - semantic version (i.e. "2.1.12") // - integer (i.e. "45") // - git SHA (i.e. "3da541559918a808c2402bba5012f6c60b27661c") // If you have multiple code versions that are relevant, those can be sent inside "client" and "server" // (see those sections below) // For most cases, just send it here. "code_version": "3da541559918a808c2402bba5012f6c60b27661c", // Optional: platform // The platform on which this occurred. Meaningful platform names: // "browser", "android", "ios", "flash", "client", "heroku", "google-app-engine" // If this is a client-side event, be sure to specify the platform and use a post_client_item access token. "platform": "linux", // Optional: language // The name of the language your code is written in. // This can affect the order of the frames in the stack trace. The following languages set the most // recent call first - 'ruby', 'javascript', 'php', 'java', 'objective-c', 'lua' // It will also change the way the individual frames are displayed, with what is most consistent with // users of the language. "language": "python", // Optional: framework // The name of the framework your code uses "framework": "pyramid", // Optional: context // An identifier for which part of your application this event came from. // Items can be searched by context (prefix search) // For example, in a Rails app, this could be `controller#action`. // In a single-page javascript app, it could be the name of the current screen or route. "context": "project#index", // Optional: request // Data about the request this event occurred in. "request": { // Can contain any arbitrary keys. Rollbar understands the following: // url: full URL where this event occurred "url": "https://rollbar.com/project/1", // method: the request method "method": "GET", // headers: object containing the request headers. "headers": { // Header names should be formatted like they are in HTTP. "Accept": "text/html", "Referer": "https://rollbar.com/" }, // params: any routing parameters (i.e. for use with Rails Routes) "params": { "controller": "project", "action": "index" }, // GET: query string params "GET": {}, // query_string: the raw query string "query_string": "", // POST: POST params "POST": {}, // body: the raw POST body "body": "", // user_ip: the user's IP address as a string. // Can also be the special value "$remote_ip", which will be replaced with the source IP of the API request. // Will be indexed, as long as it is a valid IPv4 address. "user_ip": "100.51.43.14" }, // Optional: person // The user affected by this event. Will be indexed by ID, username, and email. // People are stored in Rollbar keyed by ID. If you send a multiple different usernames/emails for the // same ID, the last received values will overwrite earlier ones. "person": { // Required: id // A string up to 40 characters identifying this user in your system. "id": "12345", // Optional: username // A string up to 255 characters "username": "brianr", // Optional: email // A string up to 255 characters "email": "brian@rollbar.com" }, // Optional: server // Data about the server related to this event. "server": { // Can contain any arbitrary keys. Rollbar understands the following: // Optional: cpu // A string up to 255 characters "cpu": "x64", // Optional: host // host: The server hostname. Will be indexed. "host": "web4", // Optional: root // root: Path to the application code root, not including the final slash. // Used to collapse non-project code when displaying tracebacks. "root": "/Users/brian/www/mox", // Optional: Branch // branch: Name of the checked-out source control branch. Defaults to "master" "branch": "master", // Optional: code_version // String describing the running code version on the server // See note about "code_version" above "code_version": "b6437f45b7bbbb15f5eddc2eace4c71a8625da8c", // (Deprecated) sha: Git SHA of the running code revision. Use the full sha. "sha": "b6437f45b7bbbb15f5eddc2eace4c71a8625da8c" }, // Optional: client // Data about the client device this event occurred on. // As there can be multiple client environments for a given event (i.e. Flash running inside // an HTML page), data should be namespaced by platform. "client": { // Can contain any arbitrary keys. Rollbar understands the following: // Optional: cpu // A string up to 255 characters "cpu": "x64", "javascript": { // Optional: browser // The user agent string "browser": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3)", // Optional: code_version // String describing the running code version in javascript // See note about "code_version" above "code_version": "b6437f45b7bbbb15f5eddc2eace4c71a8625da8c", // Optional: source_map_enabled // Set to true to enable source map deobfuscation // See the "Source Maps" guide for more details. "source_map_enabled": false, // Optional: guess_uncaught_frames // Set to true to enable frame guessing // See the "Source Maps" guide for more details. "guess_uncaught_frames": false } }, // Optional: custom // Any arbitrary metadata you want to send. "custom" itself should be an object. "custom": {}, // Optional: fingerprint // A string controlling how this occurrence should be grouped. Occurrences with the same // fingerprint are grouped together. See the "Grouping" guide for more information. // Should be a string up to 40 characters long; if longer than 40 characters, we'll use its SHA1 hash. // If omitted, we'll determine this on the backend. "fingerprint": "50a5ef9dbcf9d0e0af2d4e25338da0d430f20e52", // Optional: title // A string that will be used as the title of the Item occurrences will be grouped into. // Max length 255 characters. // If omitted, Rollbar will determine this on the backend. "title": "NameError when setting last project in views/project.py", // Optional: uuid // A string, up to 36 characters, that uniquely identifies this occurrence. // While it can now be any latin1 string, this may change to be a 16 byte field in the future. // We recommend using a UUID4 (16 random bytes). // The UUID space is unique to each project, and can be used to look up an occurrence later. // It is also used to detect duplicate requests. If you send the same UUID in two payloads, the second // one will be discarded. // While optional, it is recommended that all clients generate and provide this field "uuid": "f81d4fae-7dec-11d0-a765-00a0c91e6bf6", // Optional: notifier // Describes the library used to send this event. "notifier": { // Optional: name // Name of the library "name": "pyrollbar", // Optional: version // Library version string "version": "1.0.0" } } } ``` Note that you can send us whatever data you want and we'll store it. Max payload size is 1024kb (kilobytes). For best results, put custom data in `request`, `server`, `client`, `person`, or `custom`. ### Response Format #### Success On success, this endpoint will respond with HTTP status code 200, and a JSON response like the following: ```javascript { // Always present: err // 0 indiciates that there was no error err: 0, // Always present: result result: { // Always present: uuid // UUID of the posted occurrence. // If you provided one in the payload, this will be the value you provided // If you did not, one will be generated for you. // You can use this later to look up the occurrence by UUID. uuid: "d4c7acef55bf4c9ea95e4fe9428a8287", // Deprecated: id // Unused; will be removed in the future id: null } } ``` On error, this endpoint will respond with an HTTP error code 400 or higher, and a JSON response like the following: ```javascript { // Always present: err // 1 indicates there was an error err: 1, // Always present: message // A human-readable message describing the error message: "request entity too large" } ``` DIFFERENT TOKEN FAMILY: this is one of only three tools that need a PROJECT access token minted with the `post_server_item` scope (Rollbar dashboard -> the project -> Settings -> Project Access Tokens). An ACCOUNT token -- the one that reaches most of this integration -- is not recognised on this route at all and answers 403 'access token not found', a project `read`+`write` token answers 403 'post_server_item scope is required', and Rollbar REFUSES to mint a token holding `post_server_item` alongside `read` or `write` (400 'Invalid scope combination', measured 2026-09-24). So a connection that can call this tool is a SEPARATE connection that can call almost nothing else; that is Rollbar's rule, not Agentic Fabriq's.

Get metrics for a list of items via POST /api/1/metrics/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 project_id. PASS `project_id` WHEN THE CONNECTION HOLDS AN ACCOUNT TOKEN. Rollbar documents no `project_id` for this operation and refuses an account token without one -- 403 'Requires project access', measured 2026-09-24 -- while accepting the parameter it does not document. `List all projects` returns the ids. A connection holding a PROJECT access token is already scoped to one project and may omit it.

Occurrences over a span of time via POST /api/1/metrics/occurrences. Get occurrences metrics over a span of time by filtering, grouping, and aggregating. The endpoint follows search/query semantics as a POST request using project read access token. List of **columns/fields** that can be used with some components of your query: * `project_id` * `item_id` * `environment` * `browser_family` * `browser_version` * `os_family` * `os_version` * `device_brand` * `device_model` * `ip_address` * `item_status` * `item_level` * `item_group_item_id` * `item_title` * `item_counter` * `person_username` * `person_email` * `person_id` * `code_version` * `count` * `occurrence_id` * `uuid` * `context` * `platform` * `framework` * `platform_canonical` * `framework_canonical` * `language` * `language_name` * `notifier_name` * `notifier_version` * `occurrence_count` * `message_body` * `timestamp` * `fingerprint` * `server_host` * `server_root` * `server_pid` * `server_cpu` * `scm_branch` * `request_url` * `request_method` * `request_query_string` * `request_body`

Get resolution time metrics for a list of projects via POST /api/1/metrics/ttr. Get resolution time metrics for a provided list of project IDs. It can be filtered by environments, levels and frameworks.

Create email notification rules via POST /api/1/notifications/email/rules. Create Email notification rules

Create Slack notification rules via POST /api/1/notifications/slack/rules. Create Slack notification rules

Create webhook notification rules via POST /api/1/notifications/webhook/rules. Create Webhook notification rules

Request person deletion via POST /api/1/people/delete_jobs. 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` * `person_id` These correspond to the values transmitted in the original occurrences (see the docs for [Create item](ref:create-item)) and can also be found by viewing any tracked person via the [People Tracking](doc:person-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 } } ```

Create a project access token via POST /api/1/project/{project_id}/access_tokens. Mint a new access token on one project. `scopes` picks what it may do -- `read`, `write`, `post_server_item` or `post_client_item` -- and `name` labels it. THE NEW TOKEN'S VALUE IS REDACTED FROM THIS RESULT and Rollbar never returns it again: tokens created since April 2025 are encrypted and are not retrievable from the UI or the API after creation. Everything else about the token comes back, including the `public_id` the rate-limit and delete operations address it by. If you need the token value itself, create it in the Rollbar UI, where it is shown once. THE TOKEN VALUE IS REDACTED FROM THIS RESULT. Rollbar returns the `access_token` field as a live credential, and Agentic Fabriq replaces it before the reply leaves the connector, because a tool result reaches the model's context and the audit pipeline. Everything else -- the `public_id`, the scopes, the status, the rate-limit window -- is returned untouched. Rollbar shows a token's value only once, at creation, and encrypts it afterwards, so if you need the value itself, mint the token in the Rollbar dashboard where it is displayed.

Create a project via POST /api/1/projects. Create a project on the account. `name` is required; `source_project_id` copies settings from an existing project. The reply carries the new project's id, which the project operations then take. A fresh project is created with its own onboarding access tokens, which `List all project access tokens` reports.

Cancel an RQL job via POST /api/1/rql/job/{job_id}/cancel. # Response The response will be a RQL Job resource, example: ```json { "err" 0, "result": { "id": 123, // job id "project_id": 456, "query_string": "show tables", "status": "cancelled", // One of "new", "running", "success", "failed", "cancelled", or "timed_out" "job_hash": "abcdefabcdefabcdef", "date_created": 1446598885, "date_modified": 1446598885 } }```

Create an RQL job via POST /api/1/rql/jobs. # Response The response will be a RQL Job resource, example: ```json { "err" 0, "result": { "id": 123, // job id "project_id": 456, "query_string": "show tables", "status": "new", // One of "new", "running", "success", "failed", "cancelled", or "timed_out" "job_hash": "abcdefabcdefabcdef", "date_created": 1446598885, "date_modified": 1446598885 } }```

Create a service link via POST /api/1/service_links. Create Service Links PASS `project_id` WHEN THE CONNECTION HOLDS AN ACCOUNT TOKEN. Rollbar documents no `project_id` for this operation and refuses an account token without one -- 403 'Requires project access', measured 2026-09-24 -- while accepting the parameter it does not document. `List all projects` returns the ids. A connection holding a PROJECT access token is already scoped to one project and may omit it.

Invite an email address to a team via POST /api/1/team/{team_id}/invites. 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, "from_user_id": 5325, "team_id": 272686, "to_email": "gilfoyle@piedpiper.com", "status": "pending", "date_created": 1519946545, "date_redeemed": null } } ```

Create a team via POST /api/1/teams. # 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.

Configure email notifications via PUT /api/1/notifications/email. Configuring Email Notifications integration PASS `project_id` WHEN THE CONNECTION HOLDS AN ACCOUNT TOKEN. Rollbar documents no `project_id` for this operation and refuses an account token without one -- 403 'Requires project access', measured 2026-09-24 -- while accepting the parameter it does not document. `List all projects` returns the ids. A connection holding a PROJECT access token is already scoped to one project and may omit it.

Update an email notification rule via PUT /api/1/notifications/email/rule/{rule_id}. Update a notification rule by ID PASS `project_id` WHEN THE CONNECTION HOLDS AN ACCOUNT TOKEN. Rollbar documents no `project_id` for this operation and refuses an account token without one -- 403 'Requires project access', measured 2026-09-24 -- while accepting the parameter it does not document. `List all projects` returns the ids. A connection holding a PROJECT access token is already scoped to one project and may omit it.

Replace all email notification rules via PUT /api/1/notifications/email/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/{rule_id}` endpoint instead. To add new rules, use the `POST` endpoint. REPLACES THE WHOLE COLLECTION: the array sent becomes the complete set of rules for this channel, so any existing rule not included in it is deleted. Read the current rules with the matching List tool and send them back alongside the new one, or use the Create tool, which appends.

Configure the PagerDuty integration via PUT /api/1/notifications/pagerduty. Configuring PagerDuty integration PASS `project_id` WHEN THE CONNECTION HOLDS AN ACCOUNT TOKEN. Rollbar documents no `project_id` for this operation and refuses an account token without one -- 403 'Requires project access', measured 2026-09-24 -- while accepting the parameter it does not document. `List all projects` returns the ids. A connection holding a PROJECT access token is already scoped to one project and may omit it.

Update a PagerDuty notification rule via PUT /api/1/notifications/pagerduty/rule/{rule_id}. Update a notification rule by ID PASS `project_id` WHEN THE CONNECTION HOLDS AN ACCOUNT TOKEN. Rollbar documents no `project_id` for this operation and refuses an account token without one -- 403 'Requires project access', measured 2026-09-24 -- while accepting the parameter it does not document. `List all projects` returns the ids. A connection holding a PROJECT access token is already scoped to one project and may omit it.

Replace all PagerDuty notification rules via PUT /api/1/notifications/pagerduty/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/{rule_id}` endpoint instead. To add new rules, use the `POST` endpoint. REPLACES THE WHOLE COLLECTION: the array sent becomes the complete set of rules for this channel, so any existing rule not included in it is deleted. Read the current rules with the matching List tool and send them back alongside the new one, or use the Create tool, which appends.

Configure the Slack integration via PUT /api/1/notifications/slack. Configuring Slack integration PASS `project_id` WHEN THE CONNECTION HOLDS AN ACCOUNT TOKEN. Rollbar documents no `project_id` for this operation and refuses an account token without one -- 403 'Requires project access', measured 2026-09-24 -- while accepting the parameter it does not document. `List all projects` returns the ids. A connection holding a PROJECT access token is already scoped to one project and may omit it.

Update a Slack notification rule via PUT /api/1/notifications/slack/rule/{rule_id}. Update a notification rule by ID PASS `project_id` WHEN THE CONNECTION HOLDS AN ACCOUNT TOKEN. Rollbar documents no `project_id` for this operation and refuses an account token without one -- 403 'Requires project access', measured 2026-09-24 -- while accepting the parameter it does not document. `List all projects` returns the ids. A connection holding a PROJECT access token is already scoped to one project and may omit it.

Replace all Slack notification rules via PUT /api/1/notifications/slack/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/{rule_id}` endpoint instead. To add new rules, use the `POST` endpoint. REPLACES THE WHOLE COLLECTION: the array sent becomes the complete set of rules for this channel, so any existing rule not included in it is deleted. Read the current rules with the matching List tool and send them back alongside the new one, or use the Create tool, which appends.

Configure the webhook integration via PUT /api/1/notifications/webhook. Configuring Webhook integration PASS `project_id` WHEN THE CONNECTION HOLDS AN ACCOUNT TOKEN. Rollbar documents no `project_id` for this operation and refuses an account token without one -- 403 'Requires project access', measured 2026-09-24 -- while accepting the parameter it does not document. `List all projects` returns the ids. A connection holding a PROJECT access token is already scoped to one project and may omit it.

Update a webhook notification rule via PUT /api/1/notifications/webhook/rule/{rule_id}. Update a notification rule by ID PASS `project_id` WHEN THE CONNECTION HOLDS AN ACCOUNT TOKEN. Rollbar documents no `project_id` for this operation and refuses an account token without one -- 403 'Requires project access', measured 2026-09-24 -- while accepting the parameter it does not document. `List all projects` returns the ids. A connection holding a PROJECT access token is already scoped to one project and may omit it.

Replace all webhook notification rules via PUT /api/1/notifications/webhook/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/{rule_id}` endpoint instead. To add new rules, use the `POST` endpoint. REPLACES THE WHOLE COLLECTION: the array sent becomes the complete set of rules for this channel, so any existing rule not included in it is deleted. Read the current rules with the matching List tool and send them back alongside the new one, or use the Create tool, which appends.

Replace a service link via PUT /api/1/service_links/{id}. Replace existing Service Link PASS `project_id` WHEN THE CONNECTION HOLDS AN ACCOUNT TOKEN. Rollbar documents no `project_id` for this operation and refuses an account token without one -- 403 'Requires project access', measured 2026-09-24 -- while accepting the parameter it does not document. `List all projects` returns the ids. A connection holding a PROJECT access token is already scoped to one project and may omit it.

Assign a team to a project via PUT /api/1/team/{team_id}/project/{project_id}. # Example Response ```json { "err": 0, "result": { "team_id": 272686, "project_id": 165090 } } ```

Assign a user to team via PUT /api/1/team/{team_id}/user/{user_id}. Assign a user to a team, granting them the team's access level in every project that team is assigned to. Idempotent: assigning a user who is already on the team answers 200 with the same pair.