Source
API documentation — FireHydrant
Checked for FireHydrant on 6 Nov 2026
- Page
- https://docs.firehydrant.com/reference/firehydrant-api
- Checked
- 6 Nov 2026, 04:30 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:c936a0d6ea112e9fc8c9faeb0a6c5441a66b960aaec99c7ce1283fc0f5619110
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
API style Report an error
“The FireHydrant API is based around REST. It uses Bearer token authentication and returns JSON responses.”
-
API base endpoint Report an error
“https://api.firehydrant.io/v1”
-
API read only endpoint Report an error
“Note that the read-only endpoint has a much longer timeout for retrieving more complex data, but may lag behind the primary endpoint by as much as 30s. Any attempt to send POST, PATCH, PUT, or DELETE methods will result in an error.”
-
API keys owner permission Report an error
“To access the FireHydrant API, you must authenticate with an API key (requires Owner permissions in your organization to manage).”
-
API rate limit Report an error
“As of February 7th, 2023, the rate limit is 50 requests per account every 10 seconds, or 300 requests per minute.”
-
API pagination Report an error
“(The per-page default for the array is 20 items.)”
-
API authentication header Report an error
“All requests to the FireHydrant API require an Authorization header with the value set to Bearer {token}.”
13 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 Integrations, API & administration
- The SRE Lead Integrations, API & administration