# Raygun API V3 for coding agents

Use Raygun API V3 and OpenAPI documentation for custom workflows, CI checks, and observability automation.

## When to use API V3

Use API V3 for custom workflows, typed integrations, CI release-regression checks, internal dashboards, and deterministic automation. Use remote MCP instead when a coding agent needs a ready-to-use Raygun tool layer.

## Authentication

API V3 requests use Bearer authentication with a Raygun Personal Access Token (PAT). Create a PAT in Raygun account settings and grant only the scopes required by the workflow.

```bash
curl "https://api.raygun.com/v3/applications?offset=0&count=20" \
  -H "Authorization: Bearer $RAYGUN_PAT" \
  -H "Accept: application/json"
```

## Security practices

- Request only the scopes required by the workflow.
- Store PATs in a secret manager or local agent configuration.
- Never paste a PAT into chat or commit it to a repository.
- Rotate tokens when people, teammates, or automation scopes change.
- Review generated fixes before merging or deploying.

## Endpoint coverage

- Applications and access
- Crash Reporting error groups
- Deployment tracking
- Real user sessions and performance
- Teams, users, and collaboration
- Metrics, histograms, and exports

## References

- API documentation: https://raygun.com/documentation/product-guides/raygun-api/
- OpenAPI specification: https://api.raygun.com/v3/raygun-openapi-spec.json
- Create a PAT: https://app.raygun.com/user/tokens?utm_source=ai.raygun.com&utm_medium=agent_portal&utm_campaign=pat
- Remote MCP: https://ai.raygun.com/mcp