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

ilert Event Flows API

The Event Flows API from ilert — 2 operation(s) for event flows.

ilert Event Flows API is one of 33 APIs that ilert publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Event Flows. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, rate-limit docs, and 1 JSON Schema.

This API exposes 5 operations across 2 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version v2.2026.5-r.3.

Requests are made against a single base URL, /api.

5 operations 2 paths 14 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2.2026.5-r.3
Base URL
https://api.ilert.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

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

  • apiKey — The Bearer API key of your user more info .

Paths & Operations 5

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

Event Flows 5
GET
/event-flows
List existing event flows.
2 params → 200
POST
/event-flows
Create a new event flow.
body → 201
GET
/event-flows/{id}
Get a specific event flow.
1 param → 200
PUT
/event-flows/{id}
Update a specific event flow.
1 param body → 200
DELETE
/event-flows/{id}
Delete a specific event flow.
1 param → 204

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are EventFlowNodeRule (9 properties), EventFlowNode (5 properties), EventFlow (4 properties), EventFlowBranch (4 properties). Each schema is shown below with its type and property counts.

EventFlow
object
4 properties 2 required
EventFlowNodeMetadataWait
object
3 properties
EventFlowNodeMetadataTransform
object
2 properties
EventFlowNode
object
5 properties 1 required
DynamicValue
EventFlowNodeMetadataDefineBranches
object
1 property
EventFlowNodeMetadata
EventFlowBranch
object
4 properties 1 required
EventFlowNodeDefinition
object
2 properties 1 required
EventFlowNodeMetadataRouteEvent
object
3 properties 1 required
TeamRel
object
2 properties
EventFlowListItem
object
3 properties
EventFlowNodeRule
object
9 properties 3 required
EventFlowNodeMetadataSupportHours
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ilert-event-flows-api-openapi.yml Raw ↑

Other APIs ilert publishes across the network.

ilert Alert Actions API
ilert Alert Sources API
ilert Alerts API
ilert Call Flow Numbers API
ilert Call Flows API
ilert Connectors API
ilert Contacts API
ilert Deployment Events API
ilert Deployment Pipelines API
ilert Escalation Policies API
ilert Events API
ilert Heartbeat Monitors API
Where this information came from

This is an independent, third-party profile of ilert Event Flows 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.