Telnyx

Telnyx MDR Detail Reports API

The MDR Detail Reports API from Telnyx — 1 operation(s) for mdr detail reports.

GitHub OpenAPI

Operations 1

GET /reports/mdrs Fetch all Mdr records #

Documentation

📖
Documentation
https://developers.telnyx.com/api

Specifications

⚙
OpenAPI
https://artifacts.apis.io/telnyx/openapi/telnyx-mdr-detail-reports-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/telnyx/json-schema/telnyx-mdr-get-detail-response-schema.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/telnyx:telnyx-mdr-detail-reports-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

telnyx-mdr-detail-reports-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Telnyx MDR Detail Reports API
  version: 2.0.0
  contact:
    email: support@telnyx.com
  x-endpoint-cost: light
  x-refined-note:
  - x-latency-category differs across the merged source definitions and was not carried
  description: 'Operations tagged MDR Detail Reports across 3 of this provider''s published API definitions: telnyx-openapi.json, telnyx-openapi.yml, telnyx-openapi_2.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.telnyx.com/v2
  description: Version 2.0.0 of the Telnyx API
security:
- bearerAuth: []
tags:
- name: MDR Detail Reports
paths:
  /reports/mdrs:
    get:
      tags:
      - MDR Detail Reports
      description: Returns message detail records (MDRs) matching the provided criteria, such as date range, direction, status, and message type.
      summary: Fetch all Mdr records
      operationId: GetPaginatedMdrs
      parameters:
      - name: start_date
        in: query
        description: Pagination start date
        schema:
          type: string
      - name: end_date
        in: query
        description: Pagination end date
        schema:
          type: string
      - name: id
        in: query
        description: Filter results by identifier.
        schema:
          type: string
          description: Message uuid
          example: e093fbe0-5bde-11eb-ae93-0242ac130002
      - name: direction
        in: query
        description: Filter results by direction.
        schema:
          type: string
          description: Direction (inbound or outbound)
          example: INBOUND
          enum:
          - INBOUND
          - OUTBOUND
      - name: profile
        in: query
        description: Filter results by profile.
        schema:
          type: string
          description: Name of the profile
          example: My profile
      - name: cld
        in: query
        description: Filter results by cld.
        schema:
          type: string
          description: Destination number
          example: '+15551237654'
      - name: cli
        in: query
        description: Filter results by cli.
        schema:
          type: string
          description: Origination number
          example: '+15551237654'
      - name: status
        in: query
        description: Filter results by status.
        schema:
          type: string
          description: Message status
          example: DELIVERED
          enum:
          - GW_TIMEOUT
          - DELIVERED
          - DLR_UNCONFIRMED
          - DLR_TIMEOUT
          - RECEIVED
          - GW_REJECT
          - FAILED
      - name: message_type
        in: query
        description: Filter results by message type.
        schema:
          type: string
          description: Type of message
          example: SMS
          enum:
          - SMS
          - MMS
      responses:
        '200':
          description: Successful
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/reporting_MdrGetDetailResponse'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/reporting_ErrorResponse_77109e5d17'
      x-latency-category: interactive
    servers:
    - url: https://api.telnyx.com/v2
      description: Version 2.0.0 of the Telnyx API
components:
  schemas:
    reporting_Error_77109e5d17:
      type: object
      properties:
        code:
          type: string
          example: '10011'
        title:
          type: string
          example: Bad Request
        detail:
          type: string
          example: Invalid parameter value
    MdrDetailResponse:
      type: object
      properties:
        created_at:
          type: string
          description: Message sent time
          format: date-time
          example: '2020-07-01T00:00:00-06:00'
        profile_name:
          type: string
          description: Configured profile name. New profiles can be created and configured on Telnyx portal
          example: configured-profile-name
        direction:
          type: string
          description: Direction of message - inbound or outbound.
          example: outbound
        parts:
          type: number
          description: Number of parts this message has. Max number of character is 160. If message contains more characters then that it will be broken down in multiple parts
          example: 2
        status:
          type: string
          description: Message status
          example: DELIVERED
          enum:
          - GW_TIMEOUT
          - DELIVERED
          - DLR_UNCONFIRMED
          - DLR_TIMEOUT
          - RECEIVED
          - GW_REJECT
          - FAILED
        cld:
          type: string
          description: The destination number for a call, or the callee
          example: '+1555123456'
        cli:
          type: string
          description: The number associated with the person initiating the call, or the caller
          example: '+1555123456'
        rate:
          type: string
          description: Rate applied to the message
          example: '0.05'
        cost:
          type: string
          description: Final cost. Cost is calculated as rate * parts
          example: '0.1'
        currency:
          type: string
          description: Currency of the rate and cost
          example: USD
          enum:
          - AUD
          - CAD
          - EUR
          - GBP
          - USD
        id:
          type: string
          description: Id of message detail record
          example: 99b637f3-07fd-45ac-b9ca-b87208c24650
        message_type:
          type: string
          description: Type of message
          example: SMS
          enum:
          - SMS
          - MMS
        record_type:
          type: string
          example: mdr_report
    reporting_PaginationMeta_77109e5d17:
      type: object
      properties:
        total_pages:
          type: integer
          format: int32
          example: 3
        total_results:
          type: integer
          format: int32
          example: 55
        page_number:
          type: integer
          format: int32
          example: 2
        page_size:
          type: integer
          format: int32
          example: 25
    reporting_MdrGetDetailResponse:
      type: object
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/MdrDetailResponse'
        meta:
          $ref: '#/components/schemas/reporting_PaginationMeta_77109e5d17'
    reporting_ErrorResponse_77109e5d17:
      type: object
      properties:
        errors:
          type: array
          items:
            $ref: '#/components/schemas/reporting_Error_77109e5d17'
    reporting_PaginationMeta:
      properties:
        page_number:
          example: 2
          format: int32
          type: integer
        page_size:
          example: 25
          format: int32
          type: integer
        total_pages:
          example: 3
          format: int32
          type: integer
        total_results:
          example: 55
          format: int32
          type: integer
      type: object
    reporting_ErrorResponse:
      properties:
        errors:
          items:
            $ref: '#/components/schemas/reporting_Error'
          type: array
      type: object
    reporting_Error:
      properties:
        code:
          example: '10011'
          type: string
        detail:
          example: Invalid parameter value
          type: string
        title:
          example: Bad Request
          type: string
      type: object
    MdrGetDetailResponse:
      properties:
        data:
          items:
            $ref: '#/components/schemas/MdrDetailResponse'
          type: array
        meta:
          $ref: '#/components/schemas/reporting_PaginationMeta'
      type: object
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: API key
      description: 'Telnyx API key supplied as `Authorization: Bearer <token>`. In production, auth may be validated by the API gateway and forwarded via Telnyx auth headers.'
    Payment:
      type: apiKey
      in: header
      name: Authorization
      description: 'Machine Payment Protocol credential used on paid retries, sent as `Authorization: Payment ...`. Obtained by paying a challenge returned in the `WWW-Authenticate` header of a 402 response. This is not a Telnyx API key; initial challenge requests use standard bearer authentication instead.'
    agent-memory_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key
    bearerAuth:
      type: http
      scheme: bearer
    branded-calling_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key. Generate one at https://portal.telnyx.com/#/app/api-keys.
    collections_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key. Collections and results are automatically scoped to the authenticated user's organization.
    number-reputation_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key. Generate one at https://portal.telnyx.com/#/app/api-keys.
    oauthClientAuth:
      type: oauth2
      flows:
        clientCredentials:
          tokenUrl: https://api.telnyx.com/v2/oauth/token
          scopes:
            admin: Administrative access to Telnyx resources
        authorizationCode:
          authorizationUrl: https://api.telnyx.com/v2/oauth/authorize
          tokenUrl: https://api.telnyx.com/v2/oauth/token
          refreshUrl: https://api.telnyx.com/v2/oauth/token
          scopes:
            admin: Administrative access to Telnyx resources
      description: OAuth 2.0 authentication for Telnyx API and MCP integrations
    outbound-voice-profiles_bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    pronunciation-dicts_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API v2 key. Obtain from https://portal.telnyx.com
    rcs-registration_bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: API key
    stored-payment-transactions_bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    transcriptions-search_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key. Results are automatically scoped to the authenticated user's organization.
    web-search_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key
    pay-connectors_bearerAuth:
      type: http
      scheme: bearer
      description: Telnyx API key, not the processor bearer token.
    telnyxApiKey:
      type: http
      scheme: bearer
      description: Management-only Telnyx account credential.
x-refined-from:
- telnyx-openapi.json
- telnyx-openapi.yml
- telnyx-openapi_2.json
x-service-info:
  categories:
  - communication
  - developer-tools
  docs:
    apiReference: https://developers.telnyx.com
    homepage: https://telnyx.com
    llms: https://telnyx.com/llms.txt