How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Raygun Errors API

Triage error groups and instances — list, get, resolve, activate, ignore, permanently ignore, and comment on grouped errors. Drill into individual error instances with full stack-trace, environment, request, and breadcrumb context.

Raygun Errors API is one of 15 APIs that Raygun publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Observability, Crash Reporting, Errors, and Error Groups. The published artifact set on APIs.io includes API documentation, an OpenAPI specification, and 1 JSON Schema.

This API exposes 12 operations across 12 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 3.0.

Requests are made against a single base URL, https://api.raygun.com/v3.

12 operations 12 paths 11 schemas 7 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0
Server
https://api.raygun.com/v3
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Raygun Errors API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (personal_access_token). By default, every request must be authenticated.

  • personal_access_token — Personal Access Token authorization using the Bearer scheme. Example: Authorization: Bearer {token}

Paths & Operations 12

Across 12 paths, the API surfaces 12 operations — 7 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Errors 12
GET
/applications/{application-identifier}/error-groups
List Error Groups for an Application
list-error-groups 4 params → 200401403404429
GET
/applications/{application-identifier}/deployments/latest/error-groups
List Error Groups From the Latest Deployment
list-error-groups-from-latest-deployment 5 params → 200401403404429
GET
/applications/{application-identifier}/deployments/{deployment-identifier}/error-groups
List Error Groups From a Deployment
list-error-groups-from-deployment 6 params → 200401403404429
GET
/applications/{application-identifier}/error-groups/{error-group-identifier}
Get Error Group by Identifier
get-error-group 2 params → 200401403404429
POST
/applications/{application-identifier}/error-groups/{error-group-identifier}/resolve
Resolve Error Group
error-group-resolve 2 params body → 200401403404409422429
POST
/applications/{application-identifier}/error-groups/{error-group-identifier}/activate
Activate Error Group
error-group-activate 2 params → 200401403404409422429
POST
/applications/{application-identifier}/error-groups/{error-group-identifier}/ignore
Ignore Error Group
error-group-ignore 2 params → 200401403404409422429
POST
/applications/{application-identifier}/error-groups/{error-group-identifier}/permanently-ignore
Permanently Ignore Error Group
error-group-permanently-ignore 2 params body → 200401403404409422429
POST
/applications/{application-identifier}/error-groups/{error-group-identifier}/comment
Create Error Group Comment
error-group-create-comment 2 params body → 200401403404422429
GET
/applications/{application-identifier}/error-groups/{error-group-identifier}/instances
List Error Instances for an Error Group
list-error-instances-by-error-group-id 5 params → 200401403404429
GET
/applications/{application-identifier}/error-groups/{error-group-identifier}/instance/latest
Get Latest Error Instance for an Error Group
get-latest-error-instance-by-error-group-id 2 params → 200401403404429
GET
/applications/{application-identifier}/error-groups/{error-group-identifier}/instance/{error-instance-identifier}
Get Error Instance by Identifier
get-error-instance-by-id 3 params → 200401403404429

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are environment-detail (16 properties), error-instance (15 properties), error-group (9 properties), request-detail (8 properties). Each schema is shown below with its type and property counts.

environment-detail
object
16 properties
user-detail
object
6 properties
error-instance-summary
object
2 properties 2 required
error-instance
object
15 properties 6 required
error-detail
object
5 properties
stack-frame-detail
object
6 properties
request-detail
object
8 properties
client-detail
object
3 properties
breadcrumb-detail
object
6 properties
comment
object
4 properties 5 required
error-group
object
9 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

raygun-errors-api-openapi.yml Raw ↑

Other APIs Raygun publishes across the network.

Raygun Applications API
Raygun Deployments API
Raygun Source Maps API
Raygun Sessions API
Raygun Pages API
Raygun Customers API
Raygun Metrics API
Raygun Flutter Symbols API
Raygun Teams API
Raygun Invitations API
Raygun Plans API
Raygun Crash Reporting Ingestion API
Where this information came from

This is an independent, third-party profile of Raygun Errors API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.