The Rollbar API provides a RESTful interface to much of the data in the system. It is used by our official SDKs to report errors/exceptions, deploys, and other messages. It can be used to create SDKs for additional languages, get data out to integrate with other systems, or whatever else you can imagine. If the API is missing something you'd like to see, please let us know.
Ping
To test whether you're able to reach the API, you can run the following command:
curl 'https://api.rollbar.com/api/1/status/ping'
You will receive pong from the API if your request was successful.
Timestamps
All timestamps (inputs and outputs) are GMT unix timestamps.
Authentication
Authentication is done via access token included as the header X-Rollbar-Access-Token.
curl --header 'X-Rollbar-Access-Token: YOUR_ACCESS_TOKEN' 'https://api.rollbar.com/api/1/item/12345'
Note: Parameter-based authentication (query string or form data) is supported by some API endpoints, but is deprecated.
Access Tokens
Project and Account access tokens may be created and managed in the UI or via the API.
Project tokens are managed in Projects -> Project Access Tokens, and account tokens are managed in Settings -> Account Access Tokens.
You can have multiple active tokens of any kind, and you can delete or disable tokens. This can be used to rotate tokens or to use different tokens for different environments, each with their own user-defined rate limit.
POST client/server tokens
The post_client_item and post_server_item scopes for project tokens are used to post Rollbar items and deploys to the API, and to upload symbolication files (JS source maps, proguard, dSym, flutter).
These scopes cannot be combined with read or write scopes, and these tokens cannot be used with other API endpoints.
| Scope | Description |
|---|---|
post_server_item | Can perform all POST requests to /deploy/ and /item/. Can also be used to upload source maps (JS, proguard, dSym, flutter) |
post_client_item | Can perform POST requests to /item/, but only if the item has a client-side platform (browser, mobile). |
As client tokens often need to be embedded in publicly-visible code (i.e the HTML source of a page), an isolated post_client_item-only token is required to be used to send data from client environments (browser, mobile).
Read/Write tokens for project endpoints
Most API endpoints access data for a single project. Either a project token for the intended project may be used, or an account token may be used with a project_id in the request. Using an account token allows access to multiple projects without needing to use a different token for each project.
| Scope | Description |
|---|---|
read | Supports all GET operations at the project level. |
write | Supports all POST, PUT, PATCH, and DELETE operations at the project level. |
Read/Write tokens for account endpoints
Operations performed at the level of the account require an account-specific access token. Account access tokens can have the following scopes:
| Scope | Description |
|---|---|
read | Supports all GET operations at the account level. |
write | Supports all POST, PUT, PATCH, and DELETE operations at the account level. |
HTTP Responses
The API can return the following HTTP response codes:
| Code | Type | Description |
|---|---|---|
200 | OK | Operation was completed successfully |
400 | Bad request | A 400 error code means the request was malformed and could not be parsed. |
403 | Access denied | A 403 error code means the access token was missing, invalid, or does not have the necessary permissions. |
404 | Not found | A 404 error code means the requested resource was not found. This response will be returned if the URL is entirely invalid (i.e. /asdf), or if it is a URL that could be valid but is referencing something that does not exist (i.e. /item/12345). |
413 | Request entity too large | A 413 error code means the request exceeded the maximum size of 128KB. |
422 | Unprocessable Entity | A 422 error code means the request was parseable (i.e. valid JSON), but some parameters were missing or otherwise invalid. |
429 | Too Many Requests | If rate limiting is enabled for your access token, a 429 error code signifies that the rate limit has been reached and the item was not processed. |
Examples
| Link | Author | Language | Description |
|---|---|---|---|
| api-examples | Rollbar | Python | Examples using RQL, deploys, occurrences, and reports |
| api-people-example | Rollbar | Python | Shows how to gather the Person data for each occurrence of a list of items |
| rolltools | Jonathan Slate | Ruby | A few utilities using the Rollbar API |
Last updated: July 21, 2026
