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 Signals API

The Signals API from FireHydrant — 1 operation(s) for signals.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 33 operations across 19 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.firehydrant.io/, https://api.firehydrant.io/v1.

33 operations 19 paths 12 schemas 5 DELETE16 GET5 PATCH7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.firehydrant.io/v1
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

FireHydrant Signals API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (api_key). It accepts HTTP bearer tokens (bearerAuth).

Paths & Operations 33

Across 19 paths, the API surfaces 33 operations — 5 DELETE, 16 GET, 5 PATCH, 7 POST. Each is listed below with its method, path, parameters, and response codes.

Signals 33

Operations related to Signals

GET
/v1/signals/analytics/grouped_metrics
List grouped signal alert metrics
getSignalGroupedMetrics 11 params → 200
GET
/v1/signals/analytics/mttx
Get MTTX analytics for signals
getSignalsMttxAnalytics 11 params → 200
GET
/v1/signals/analytics/timeseries
List timeseries metrics for signal alerts
getSignalsAnalyticsTimeseries 12 params → 200
POST
/v1/signals/debugger
Debug a signal
debugSignal body → 201
GET
/v1/signals/email_targets
List email targets for signals
listSignalEmailTargets 1 param → 200
POST
/v1/signals/email_targets
Create an email target for signals
createSignalEmailTarget body → 201
GET
/v1/signals/email_targets/{id}
Get a signal email target
getSignalEmailTarget 1 param → 200
DELETE
/v1/signals/email_targets/{id}
Delete a signal email target
deleteSignalEmailTarget 1 param → 204
PATCH
/v1/signals/email_targets/{id}
Update a signal email target
updateSignalEmailTarget 1 param body → 200
GET
/v1/signals/event_sources
List event sources for signals
listSignalEventSources 4 params → 200
GET
/v1/signals/ingest_url
Get signal ingestion URL
getSignalIngestUrl 4 params → 200
GET
/v1/signals/transposers
List signal transposers
listSignalTransposers → 200
GET
/v1/signals/webhook_targets
List webhook targets for signals
listSignalWebhookTargets 3 params → 200
POST
/v1/signals/webhook_targets
Create a webhook target for signals
createSignalWebhookTarget body → 201
GET
/v1/signals/webhook_targets/{id}
Get a webhook target
getSignalsWebhookTarget 1 param → 200
DELETE
/v1/signals/webhook_targets/{id}
Delete a webhook target
deleteSignalsWebhookTarget 1 param → 204
PATCH
/v1/signals/webhook_targets/{id}
Update a webhook target
updateSignalsWebhookTarget 1 param body → 200
GET
/v1/signals_on_call
List on-call schedules
listSignalsOnCall 1 param → 200
GET
/v1/teams/{team_id}/escalation_policies
List escalation policies for a team
listTeamEscalationPolicies 4 params → 200
POST
/v1/teams/{team_id}/escalation_policies
Create an escalation policy for a team
createTeamEscalationPolicy 1 param body → 201
GET
/v1/teams/{team_id}/escalation_policies/{id}
Get an escalation policy for a team
getTeamEscalationPolicy 2 params → 200
DELETE
/v1/teams/{team_id}/escalation_policies/{id}
Delete an escalation policy for a team
deleteTeamEscalationPolicy 2 params → 204
PATCH
/v1/teams/{team_id}/escalation_policies/{id}
Update an escalation policy for a team
updateTeamEscalationPolicy 2 params body → 200
GET
/v1/teams/{team_id}/on_call_schedules/{schedule_id}
Get an on-call schedule for a team
getTeamOnCallSchedule 2 params → 200
DELETE
/v1/teams/{team_id}/on_call_schedules/{schedule_id}
Delete an on-call schedule for a team
deleteTeamOnCallSchedule 2 params → 204
PATCH
/v1/teams/{team_id}/on_call_schedules/{schedule_id}
Update an on-call schedule for a team
updateTeamOnCallSchedule 2 params body → 200
POST
/v1/teams/{team_id}/on_call_schedules/{schedule_id}/shifts
Create a shift for an on-call schedule
createTeamOnCallScheduleShift 2 params body → 201
GET
/v1/teams/{team_id}/signal_rules
List signal rules for a team
listTeamSignalRules 4 params → 200
POST
/v1/teams/{team_id}/signal_rules
Create a signal rule for a team
createTeamSignalRule 1 param body → 201
GET
/v1/teams/{team_id}/signal_rules/{id}
Get a signal rule
getTeamSignalRule 2 params → 200
DELETE
/v1/teams/{team_id}/signal_rules/{id}
Delete a signal rule
deleteTeamSignalRule 2 params → 204
PATCH
/v1/teams/{team_id}/signal_rules/{id}
Update a signal rule
updateTeamSignalRule 2 params body → 200
POST
/signals/events
Ingest a Signals alert event
createSignalsEvent body → 202

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are patchV1TeamsTeamIdOnCallSchedulesScheduleId (10 properties), postV1SignalsEmailTargets (9 properties), patchV1SignalsEmailTargetsId (9 properties), postV1TeamsTeamIdSignalRules (6 properties). Each schema is shown below with its type and property counts.

patchV1TeamsTeamIdOnCallSchedulesScheduleId
object
Update a Signals on-call schedule by ID
10 properties
postV1TeamsTeamIdSignalRules
object
Create a Signals rule for a team.
6 properties 4 required
postV1SignalsWebhookTargets
object
Create a Signals webhook target.
4 properties 2 required
patchV1TeamsTeamIdSignalRulesId
object
Update a Signals rule by ID
6 properties
postV1TeamsTeamIdOnCallSchedulesScheduleIdShifts
object
Create a Signals on-call shift in a schedule.
3 properties 2 required
postV1SignalsDebugger
object
2 properties 2 required
patchV1SignalsEmailTargetsId
object
Update a Signals email target by ID
9 properties
postV1SignalsEmailTargets
object
Create a Signals email target for a team.
9 properties 1 required
Signals_API_IngestKeyEntity
object
SignalsAPIIngestKeyEntity model
1 property
postV1TeamsTeamIdEscalationPolicies
object
Create a Signals escalation policy for a team.
6 properties 2 required
patchV1SignalsWebhookTargetsId
object
Update a Signals webhook target by ID
4 properties
patchV1TeamsTeamIdEscalationPoliciesId
object
Update a Signals escalation policy by ID
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

firehydrant-signals-api-openapi.yml Raw ↑

Other APIs FireHydrant publishes across the network.

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 Incidents 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
#Signals
← Back to F APIs
API Details
ID
firehydrant:firehydrant-signals-api
Base URL
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-signals-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/firehydrant-signals-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 Signals 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.