Caution
As of 2025-03-11, Grafana OnCall OSS has entered maintenance mode, and will be archived on 2026-03-24. No further feature development will occur; however, we will still provide fixes for critical bugs and for valid CVEs with a CVSS score of 7.0 or higher. For more information, refer to our blog post.
Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
HTTP API Reference
Use the following guidelines for the Grafana OnCall API.
Authentication
To authorize, use the Authorization header:
# With shell, you can just pass the correct header with each request
curl "api_endpoint_here" --header "Authorization: meowmeowmeow"
Note that meowmeowmeow
is a valid key for test purposes.
Replace meowmeowmeow
with your API key in production.
Grafana OnCall uses API keys to allow access to the API. You can request a new OnCall API key in the API section.
An API key is specific to a user and a Grafana stack. If you want to switch to a different team configuration, request a different API key.
Pagination
List endpoints such as List Integrations or List Alert Groups return multiple objects.
The OnCall API returns them in pages. Note that the page size may vary.
Rate Limits
Grafana OnCall provides rate limits to ensure alert group notifications will be delivered to your Slack workspace even when some integrations produce a large number of alerts.
Monitoring integrations Rate Limits
Rate limited response HTTP status: 429
API rate limits
You can reduce or increase rate limits depending on platform status.