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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
FireHydrant

FireHydrant Incidents API

The Incidents API from FireHydrant — 5 operation(s) for incidents.

Documentation Provider Profile APIs.io OpenAPI GitHub

FireHydrant Incidents API is one of 16 APIs that FireHydrant publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Incidents. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 8 operations across 5 paths, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version 1.0.

Requests are made against a single base URL, https://api.firehydrant.io/v1.

8 operations 5 paths 2 schemas 1 DELETE3 GET1 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0
Server
https://api.firehydrant.io/v1
Authentication
HTTP Bearer
Contact
FireHydrant
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 8

Across 5 paths, the API surfaces 8 operations — 1 DELETE, 3 GET, 1 PATCH, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Incidents 8
GET
/incidents
List incidents
listIncidents 5 params → 200
POST
/incidents
Declare an incident
createIncident body → 201
GET
/incidents/{incident_id}
Retrieve an incident
getIncident 1 param → 200
PATCH
/incidents/{incident_id}
Update an incident
updateIncident 1 param body → 200
DELETE
/incidents/{incident_id}
Archive an incident
archiveIncident 1 param → 204
PUT
/incidents/{incident_id}/close
Close an incident
closeIncident 1 param → 200
POST
/incidents/{incident_id}/notes
Add an incident note
createIncidentNote 1 param body → 201
GET
/incidents/{incident_id}/events
List events for an incident
listIncidentEvents 1 param → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Incident (15 properties), Pagination (7 properties). Each schema is shown below with its type and property counts.

Pagination
object
7 properties
Incident
object
15 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

firehydrant-incidents-api-openapi.yml Raw ↑

Other APIs FireHydrant publishes across the network.

FireHydrant
AE Profile APIs.io
FireHydrant Audits API
AE Profile APIs.io
FireHydrant Change Events API
AE Profile APIs.io
FireHydrant Changes API
AE Profile APIs.io
FireHydrant Conversations API
AE Profile APIs.io
FireHydrant Environments API
AE Profile APIs.io
FireHydrant Functionalities API
AE Profile APIs.io
FireHydrant Ping API
AE Profile APIs.io
FireHydrant Priorities API
AE Profile APIs.io
FireHydrant Runbooks API
AE Profile APIs.io
FireHydrant Scheduled Maintenances API
AE Profile APIs.io
FireHydrant Services API
AE Profile APIs.io
#Incidents
← Back to F APIs
API Details
ID
firehydrant:firehydrant-incidents-api
Server
https://api.firehydrant.io/v1
Docs
https://firehydrant.com
Provider
FireHydrant
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=firehydrant-incidents-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/firehydrant-incidents-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of FireHydrant Incidents 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.