Source
API documentation — Rootly
Checked for Rootly on 6 Nov 2026
- Page
- https://docs.rootly.com/api-reference/overview
- Checked
- 6 Nov 2026, 04:44 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:2afd8bc4aed28e051f823e1792d7a8900214711884b83df6768a15f35cb1b444
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
API jsonapi spec Report an error
“Rootly is using the JSON:API (https://jsonapi.org) specification”
-
API auth bearer Report an error
“All API requests use the Authorization: Bearer header over HTTPS. Rootly supports two token types”
-
Rate limit read Report an error
“There is a default limit of 3000 GET, HEAD, and OPTIONS calls per API key every minute.”
-
Rate limit write Report an error
“There is a default limit of 3000 POST, PUT, PATCH or DELETE calls per API key every minute.”
-
Rate limit alerts Report an error
“Alert creation is limited to 50 per minute per API key.”
-
Rate limit configurable Report an error
“While the limit can be configured to support higher thresholds, you must first contact your Rootly Customer Success Manager to make any adjustments.”
-
Rate limit headers Report an error
“X-RateLimit headers are included in every API response, providing real-time rate limit information”
-
Rate limit response Report an error
“When rate limits are exceeded, the API will return a 429 Too Many Requests HTTP status code”
-
Pagination Report an error
“Pagination is supported for all endpoints that return a collection of items. Pagination is controlled by the page query parameter”
-
SDK official Report an error
“Official SDKs Use the official Go and Python SDKs to integrate with the Rootly API.”
-
Openapi spec Report an error
“Download the OpenAPI/Swagger specification to explore the Rootly API endpoints or generate client libraries.”
-
Oauth oidc Report an error
“OAuth 2.0 & OpenID Connect Browser-based login, scoped third-party access, and user-independent client credentials tokens.”
-
API key types Report an error
“Rootly supports three scopes of API Keys”
-
API key global Report an error
“Global API Keys are able to interact with all entities within your Rootly instance.”
-
API key team Report an error
“Team API Keys inherit the same permissions of a Team Admin. They have full read and edit access to any Rootly entity that team owns”
-
API key personal Report an error
“Personal API Keys inherit the permissions of the user who created the API key.”
-
Chat API Report an error
“The Chat API lets your application talk to Rootly AI, with optional incident or alert context. Its endpoints are under https://api.rootly.com/v1/ai/chat”
-
Chat API enablement Report an error
“Chat API availability is controlled separately for each team. Rootly must enable the API chat rollout and API chat setting for the selected team”
-
Chat API scopes Report an error
“OAuth calls need ai.chat:write for POST and DELETE, or ai.chat:read for GET; ai.chat:write also grants read access.”
-
Catalog API Report an error
“CatalogEntities GET List Catalog Entities POST Creates a Catalog Entity”
-
API base URL Report an error
“--url https://api.rootly.com/v1/incidents”
17 facts read from this page are not shown because they could not be confirmed on the page as captured.
Scores citing this record
- The Engineering Manager Integrations, API & administration
- The ICT Risk Officer Integrations, API & administration
- The IT Operations Manager Integrations, API & administration
- The MSP NOC Lead Integrations, API & administration
- The Skeptic Alert delivery, routing & noise reduction
- The Skeptic Integrations, API & administration
- The SRE Lead Integrations, API & administration