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

Telnyx MDR Usage Reports API

Messaging usage reports

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

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

This API exposes 9 operations across 5 paths, and defines 20 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.

9 operations 5 paths 20 schemas 2 DELETE5 GET2 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
Resource Areas
1

Authentication & Security 6

Telnyx MDR Usage Reports 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 9

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

MDR Usage Reports 9

Messaging usage reports

GET
/legacy/reporting/usage_reports/messaging
List MDR usage reports
getMdrUsageReports 2 params → 200400
POST
/legacy/reporting/usage_reports/messaging
Create a new legacy usage V2 MDR report request
submitMdrUsageReport body → 200400401403500
DELETE
/legacy/reporting/usage_reports/messaging/{id}
Delete a V2 legacy usage MDR report request
deleteMdrUsageReport 1 param → 200401403404500
GET
/legacy/reporting/usage_reports/messaging/{id}
Get an MDR usage report
getMdrUsageReport 1 param → 200401403404500
GET
/reports/mdr_usage_reports
Fetch all Messaging usage reports
GetMdrUsageReports 1 param → 200400
POST
/reports/mdr_usage_reports
Create MDR Usage Report
SubmitUsageReport body → 200400
GET
/reports/mdr_usage_reports/sync
Generate and fetch MDR Usage Report
GetMDRUsageReportSync 4 params → 200400
DELETE
/reports/mdr_usage_reports/{id}
Delete MDR Usage Report
DeleteUsageReport 1 param → 200400
GET
/reports/mdr_usage_reports/{id}
Retrieve messaging report
GetUsageReport 1 param → 200400

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are MdrUsageRecord (14 properties), MdrUsageReportResponseLegacy (12 properties), MdrUsageReportResponse (12 properties), MdrUsageRequestLegacy (6 properties). Each schema is shown below with its type and property counts.

MdrPostUsageReportRequest
object
4 properties 3 required
standard_Error
object
3 properties 1 required
MdrUsageReportResponseLegacy
object
Legacy V2 MDR usage report response
12 properties
MdrDeleteUsageReportResponse
object
1 property
standard_PaginationMeta
object
4 properties
MdrUsageRecord
object
14 properties
reporting_ErrorResponse
object
1 property
MdrUsageReportResponse
object
12 properties
MdrGetUsageReportByIdResponse
object
1 property
MdrPostUsageReportResponse
object
1 property
MdrDeleteUsageReportsResponse
object
1 property
MdrPostUsageReportsResponse
object
1 property
MdrUsageRequestLegacy
object
MDR usage request parameters
6 properties 1 required
MdrGetUsageReportsByIdResponse
object
1 property
reporting_Error
object
3 properties
reporting_PaginationMeta
object
4 properties
MdrGetUsageReportsResponse
object
2 properties
standard_ErrorResponse
object
1 property
standard_MdrGetUsageReportsResponse
object
2 properties
MdrGetSyncUsageReportResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

telnyx-mdr-usage-reports-api-openapi.yml Raw ↑

Other APIs Telnyx publishes across the network.

Telnyx Access Tokens API
Telnyx Addresses API
Telnyx Advanced Number Orders API
Telnyx Assistants API
Telnyx Audio API
Telnyx Audit Logs API
Telnyx Authentication Providers API
Telnyx AutoRechargePreferences API
Telnyx Billing API
Telnyx Billing Groups API
Telnyx Brands API
Telnyx Bucket SSL Certificate API
Where this information came from

This is an independent, third-party profile of Telnyx MDR Usage Reports 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.