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
Telnyx

Telnyx Notifications API

Notification settings operations

Documentation Provider Profile APIs.io OpenAPI GitHub

Telnyx Notifications API is one of 169 APIs that Telnyx publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 16 operations across 8 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.telnyx.com/v2.

16 operations 8 paths 8 schemas 3 DELETE8 GET2 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.telnyx.com/v2
Authentication
HTTP Bearer, HTTP Bearer, OAuth 2.0, HTTP Bearer, HTTP Bearer, HTTP Bearer
Contact
support@telnyx.com
Resource Areas
1

Authentication & Security 6

Telnyx Notifications API declares 6 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It accepts HTTP bearer tokens (branded-calling_bearerAuth). It supports OAuth 2.0 (oauthClientAuth) using the authorizationCode and clientCredentials flows, exposing 1 scope. It accepts HTTP bearer tokens (JWT) (outbound-voice-profiles_bearerAuth). It accepts HTTP bearer tokens (pronunciation-dicts_bearerAuth). It accepts HTTP bearer tokens (JWT) (stored-payment-transactions_bearerAuth). By default, every request must be authenticated.

  • branded-calling_bearerAuth — API key passed as a Bearer token in the Authorization header
  • oauthClientAuth — OAuth 2.0 authentication for Telnyx API and MCP integrations
  • pronunciation-dicts_bearerAuth — Telnyx API v2 key. Obtain from https://portal.telnyx.com

Paths & Operations 16

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

Notifications 16

Notification settings operations

GET
/notification_channels
List notification channels
ListNotificationChannels 2 params → 200400422500
POST
/notification_channels
Create a notification channel
CreateNotificationChannels body → 200400422500
DELETE
/notification_channels/{id}
Delete a notification channel
DeleteNotificationChannel 1 param → 200400422500
GET
/notification_channels/{id}
Get a notification channel
GetNotificationChannel 1 param → 200400404422500
PATCH
/notification_channels/{id}
Update a notification channel
UpdateNotificationChannel 1 param body → 200400422500
GET
/notification_event_conditions
List all Notifications Events Conditions
FindNotificationsEventsConditions 2 params → 200400422500
GET
/notification_events
List all Notifications Events
FindNotificationsEvents 1 param → 200400422500
GET
/notification_profiles
List all Notifications Profiles
FindNotificationsProfiles 1 param → 200400422500
POST
/notification_profiles
Create a notification profile
CreateNotificationProfile body → 200400422500
DELETE
/notification_profiles/{id}
Delete a notification profile
DeleteNotificationProfile 1 param → 200400422500
GET
/notification_profiles/{id}
Get a notification profile
GetNotificationProfile 1 param → 200400404422500
PATCH
/notification_profiles/{id}
Update a notification profile
UpdateNotificationProfile 1 param body → 200400422500
GET
/notification_settings
List notification settings
ListNotificationSettings 2 params → 200400422500
POST
/notification_settings
Add a Notification Setting
CreateNotificationSetting body → 200201400422500
DELETE
/notification_settings/{id}
Delete a notification setting
DeleteNotificationSetting 1 param → 200201400422500
GET
/notification_settings/{id}
Get a notification setting
GetNotificationSetting 1 param → 200400404422500

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are NotificationEventCondition (12 properties), NotificationSetting (10 properties), NotificationEvent (6 properties), NotificationChannel (6 properties). Each schema is shown below with its type and property counts.

NotificationProfile
object
A Collection of Notification Channels
4 properties
NotificationSetting
object
10 properties
NotificationChannel
object
A Notification Channel
6 properties
PaginationMeta
object
4 properties
NotificationEventCondition
object
12 properties
notifications_Errors
object
1 property
NotificationEvent
object
An object representing the available notifications.
6 properties
notifications_Error
object
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

telnyx-notifications-api-openapi.yml Raw ↑

Other APIs Telnyx publishes across the network.

Telnyx Access Tokens API
AE Profile APIs.io
Telnyx Addresses API
AE Profile APIs.io
Telnyx Advanced Number Orders API
AE Profile APIs.io
Telnyx Assistants API
AE Profile APIs.io
Telnyx Audio API
AE Profile APIs.io
Telnyx Audit Logs API
AE Profile APIs.io
Telnyx Authentication Providers API
AE Profile APIs.io
Telnyx AutoRechargePreferences API
AE Profile APIs.io
Telnyx Billing API
AE Profile APIs.io
Telnyx Billing Groups API
AE Profile APIs.io
Telnyx Brands API
AE Profile APIs.io
Telnyx Bucket SSL Certificate API
AE Profile APIs.io
#Notification
← Back to T APIs
API Details
ID
telnyx:telnyx-notifications-api
Base URL
https://api.telnyx.com/v2
Docs
https://developers.telnyx.com/api
Provider
Telnyx
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=telnyx-notifications-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/telnyx-notifications-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 Telnyx Notifications 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.