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

The Contacts API from ilert — 4 operation(s) for contacts.

ilert Contacts 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 Contacts. 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 10 operations across 4 paths, and defines 5 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.

10 operations 4 paths 5 schemas 2 DELETE4 GET2 POST2 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 Contacts 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 10

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

Contacts 10
GET
/users/{user-id}/contacts/emails
Get a user's emails
1 param → 200
POST
/users/{user-id}/contacts/emails
Create a new email
1 param body → 201
GET
/users/{user-id}/contacts/emails/{id}
Get a specific email
2 params → 200
PUT
/users/{user-id}/contacts/emails/{id}
Update a user's email
2 params body → 200
DELETE
/users/{user-id}/contacts/emails/{id}
Delete the user's specified email
2 params → 204
GET
/users/{user-id}/contacts/phone-numbers
Get a user's phone numbers
1 param → 200
POST
/users/{user-id}/contacts/phone-numbers
Create a phone number
1 param body → 201
GET
/users/{user-id}/contacts/phone-numbers/{id}
Get specific phone number
2 params → 200
PUT
/users/{user-id}/contacts/phone-numbers/{id}
Update a user's phone number
2 params body → 200
DELETE
/users/{user-id}/contacts/phone-numbers/{id}
Delete the user's specified phone number
2 params → 204

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are ContactPhoneNumber (5 properties), ContactPhoneNumberPost (3 properties), ContactEmail (3 properties), ContactEmailPost (1 property). Each schema is shown below with its type and property counts.

ContactStatus
string
ContactEmail
object
3 properties
ContactPhoneNumberPost
object
3 properties
ContactPhoneNumber
object
5 properties
ContactEmailPost
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ilert-contacts-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 Deployment Events API
ilert Deployment Pipelines API
ilert Escalation Policies API
ilert Event Flows API
ilert Events API
ilert Heartbeat Monitors API
Where this information came from

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