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

FireHydrant Retrospectives API

Operations related to Retrospectives

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

Tagged areas include Retrospectives. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 14 operations across 9 paths, and defines 48 schemas. It is described by OpenAPI 3.2.0, at version 0.0.1.

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

14 operations 9 paths 48 schemas 1 DELETE5 GET3 PATCH3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

FireHydrant Retrospectives API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (api_key). By default, every request must be authenticated.

Paths & Operations 14

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

Retrospectives 14

Operations related to Retrospectives

GET
/v1/post_mortems/questions
List retrospective questions
listRetrospectiveQuestions 2 params → 200
PUT
/v1/post_mortems/questions
Update retrospective questions
updateRetrospectiveQuestions body → 200
GET
/v1/post_mortems/questions/{question_id}
Get a retrospective question
getRetrospectiveQuestion 1 param → 200
GET
/v1/post_mortems/reports
List retrospective reports
listRetrospectiveReports 4 params → 200
POST
/v1/post_mortems/reports
Create a retrospective report
createRetrospectiveReport body → 201
GET
/v1/post_mortems/reports/{report_id}
Get a retrospective report
getPostMortemReport 1 param → 200
PATCH
/v1/post_mortems/reports/{report_id}
Update a retrospective report
updatePostMortemReport 1 param body → 200
PATCH
/v1/post_mortems/reports/{report_id}/fields/{field_id}
Update a retrospective field
updateRetrospectiveField 2 params body → 200
POST
/v1/post_mortems/reports/{report_id}/publish
Publish a retrospective report
publishRetrospectiveReport 1 param body → 201400
GET
/v1/post_mortems/reports/{report_id}/reasons
List contributing factors for a retrospective report
listRetrospectiveReportReasons 3 params → 200
POST
/v1/post_mortems/reports/{report_id}/reasons
Create a contributing factor for a retrospective report
createRetrospectiveReportReason 1 param body → 201
PUT
/v1/post_mortems/reports/{report_id}/reasons/order
Update the order of contributing factors in a retrospective report
updateRetrospectiveReportReasonOrder 1 param body → 200
DELETE
/v1/post_mortems/reports/{report_id}/reasons/{reason_id}
Delete a contributing factor from a retrospective report
deleteRetrospectiveReason 2 params → 200
PATCH
/v1/post_mortems/reports/{report_id}/reasons/{reason_id}
Update a contributing factor in a retrospective report
updateRetrospectiveReason 2 params body → 200

Schemas 48

The contract defines 48 schemas that model the data the API accepts and returns. The most detailed are IncidentEntity (56 properties), Ticketing_TicketEntity (18 properties), PostMortems_PostMortemReportEntity (11 properties), CustomFields_FieldValue (9 properties). Each schema is shown below with its type and property counts.

Incidents_ChannelEntity
object
IncidentsChannelEntity model
8 properties
OrganizationEntity
object
2 properties
postV1PostMortemsReportsReportIdPublish
object
Marks an incident retrospective as published and emails all of the participants in the report the summary
2 properties
PostMortems_ReasonEntity
object
PostMortemsReasonEntity model
5 properties
SeverityMatrix_ImpactEntity
object
SeverityMatrixImpactEntity model
5 properties
Ticketing_PriorityEntity
object
TicketingPriorityEntity model
5 properties
PostMortems_PostMortemReportEntityPaginated
object
PostMortemsPostMortemReportEntityPaginated model
2 properties
IncidentEntity
object
IncidentEntity model
56 properties
Calendars_EventEntity
object
9 properties
Attachments_LinkEntity
object
AttachmentsLinkEntity model
7 properties
Incidents_ContextObjectEntity
object
4 properties
CustomFields_FieldValue
object
9 properties
patchV1PostMortemsReportsReportIdFieldsFieldId
object
Update a field value on a post mortem report
1 property 1 required
patchV1PostMortemsReportsReportId
object
Update a report
4 properties
PostMortems_QuestionEntity
object
9 properties
IncidentRoleEntity
object
IncidentRoleEntity model
7 properties
AuthorEntity
object
4 properties
Event_NoteEntity
object
EventNoteEntity model
5 properties
Incidents_LifecycleMilestoneEntity
object
9 properties
postV1PostMortemsReports
object
Create a report
1 property 1 required
PostMortems_PostMortemReportEntity
object
PostMortemsPostMortemReportEntity model
11 properties
putV1PostMortemsQuestions
object
Update the questions configured to be provided and filled out on future retrospective reports.
2 properties
postV1PostMortemsReportsReportIdReasons
object
Add a new contributing factor to an incident
1 property 1 required
PostMortems_QuestionTypeEntityPaginated
object
PostMortemsQuestionTypeEntityPaginated model
2 properties
Incidents_ImpactEntity
object
5 properties
SuccinctEntity
object
2 properties
IncidentEntity_FieldRequirementEntity
object
2 properties
ErrorEntity
object
ErrorEntity model
4 properties
Incidents_ConferenceBridgeEntity
object
2 properties
Ticketing_TicketEntity
object
TicketingTicketEntity model
18 properties
Incidents_RoleAssignmentEntity
object
IncidentsRoleAssignmentEntity model
6 properties
patchV1PostMortemsReportsReportIdReasonsReasonId
object
Update a contributing factor
1 property
PostMortems_SectionFieldEntity
object
PostMortemsSectionFieldEntity model
3 properties
Conversations_API_Entities_Reference
object
6 properties
Incidents_LifecycleMeasurementEntity
object
8 properties
Incidents_LifecyclePhaseEntity
object
6 properties
PaginationEntity
object
7 properties
IntegrationEntity
object
5 properties
Incidents_TeamAssignmentEntityLite
object
5 properties
putV1PostMortemsReportsReportIdReasonsOrder
object
Reorder a contributing factor
2 properties 2 required
UserEntity
object
UserEntity model
8 properties
PostMortems_ReasonEntityPaginated
object
PostMortemsReasonEntityPaginated model
2 properties
PostMortems_QuestionTypeEntity
object
PostMortemsQuestionTypeEntity model
6 properties
Conversations_API_Entities_Channel
object
1 property
TeamEntityLite
object
9 properties
Incidents_StatusPageEntity
object
IncidentsStatusPageEntity model
6 properties
Incidents_MilestoneEntity
object
6 properties
SeverityMatrix_ConditionEntity
object
SeverityMatrixConditionEntity model
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

firehydrant-retrospectives-api-openapi.yml Raw ↑

Other APIs FireHydrant publishes across the network.

FireHydrant Audits API
FireHydrant Change Events API
FireHydrant Changes API
FireHydrant Conversations API
FireHydrant Environments API
FireHydrant Functionalities API
FireHydrant Incidents API
FireHydrant Ping API
FireHydrant Priorities API
FireHydrant Runbooks API
FireHydrant Scheduled Maintenances API
FireHydrant Services API
Where this information came from

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