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/tata-communications-cdr-by-customer-message-id-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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

openapi: 3.2.0
info:
  version: '1.0'
  title: Mobile Messaging Exchange - CDR Report CDR by Customer Message Id API
tags:
- name: CDR by Customer Message Id
paths:
  /CDR/message/{messageId}:
    get:
      tags:
      - CDR by Customer Message Id
      summary: message logs for a message ID
      operationId: cdr_by_messageId
      parameters:
      - name: messageId
        in: path
        description: This is the customer Message Id.
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Successfully retrieved data.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SuccessResponse'
        '400':
          description: 'Request is semantically incorrect or missing required parameters. | Error: CDRs for the selected period are not loaded because the SMS retry period of 72 hours is not completed'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    SuccessResponse:
      properties:
        requestTime:
          type: string
          example: '2018-08-22T06:05:00+00:00'
          description: This is the time when request is come to the MMX Hub.
        lastDeliveredTime:
          type: string
          example: '2018-08-22T06:05:00+00:00'
          description: This is the Last delivered time.
        messageId:
          type: string
          example: b94ef907-7778-442c-9743-fe02238c6977
          description: This is the internal unique Message Id.
        accountId:
          type: string
          example: 35317-2
          description: This is the customer account id assigned to the customer at the time of onboarding. User can specify one or more custAccountId.
        destinationId:
          type: string
          example: 1-245-0
          description: This is the destination vpc
        destinationCountry:
          type: string
          example: unknown
          description: This is the destination Country
        destinationAddress:
          type: string
          example: '919961986196'
          description: This is the Destination Address.
        originatingAddress:
          type: string
          example: LNKDIN
          description: This is the Originating Address.
        attemptedStatus:
          type: string
          example: Success
          description: This is the status of attempted message.
        submittedStatus:
          type: string
          example: Success
          description: This is the status of submitted message.
        deliveredStatus:
          type: string
          example: Success
          description: This is the status of delivered message.
        errorCode:
          type: number
          example: 0.0
          description: This is the error code.
        errorDescription:
          type: string
          example: Success
          description: This is the error description.
    ErrorResponse:
      properties:
        status:
          type: string
          description: Http status of the response
        message:
          type: string
          description: Error description