Telnyx Charges Summary API
The Charges Summary API from Telnyx — 1 operation(s) for charges summary.
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/telnyx:telnyx-charges-summary-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.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Telnyx Charges Summary 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 Charges Summary across 2 of this provider''s published API definitions: telnyx-openapi.yml, telnyx-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- description: Version 2.0.0 of the Telnyx API
url: https://api.telnyx.com/v2
security:
- bearerAuth: []
tags:
- name: Charges Summary
paths:
/charges_summary:
get:
description: Retrieve a summary of monthly charges for a specified date range. The date range cannot exceed 31 days.
operationId: GetMonthlyChargesSummary
parameters:
- description: Start date for the charges summary in ISO date format (YYYY-MM-DD)
in: query
name: start_date
required: true
schema:
example: '2025-05-01'
format: date
type: string
- description: End date for the charges summary in ISO date format (YYYY-MM-DD). The date is exclusive, data for the end_date itself is not included in the report. The interval between start_date and end_date cannot exceed 31 days.
in: query
name: end_date
required: true
schema:
example: '2025-06-01'
format: date
type: string
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/MonthlyChargesSummaryResponse'
description: Monthly charges summary
'400':
$ref: '#/components/responses/charges_BadRequestErrorResponse'
'422':
$ref: '#/components/responses/charges_UnprocessableEntityErrorResponse'
default:
$ref: '#/components/responses/charges_GenericErrorResponse'
summary: Get monthly charges summary
x-latency-category: responsive
tags:
- Charges Summary
servers:
- description: Version 2.0.0 of the Telnyx API
url: https://api.telnyx.com/v2
components:
schemas:
charges_Error:
properties:
code:
format: integer
type: string
detail:
type: string
meta:
type: object
source:
properties:
parameter:
description: Indicates which query parameter caused the error.
type: string
pointer:
description: JSON pointer (RFC6901) to the offending entity.
format: json-pointer
type: string
type: object
title:
type: string
required:
- code
- title
AdjustmentLine:
properties:
amount:
description: Adjustment amount as decimal string
example: '-10.00'
type: string
description:
description: Description of the adjustment
example: Credit for service outage
type: string
event_date:
description: Date when the adjustment occurred
example: '2025-05-15'
format: date
type: string
required:
- amount
- description
- event_date
type: object
MonthlyChargesSummaryResponse:
properties:
data:
$ref: '#/components/schemas/SummaryAndTotal'
required:
- data
type: object
TotalSummary:
properties:
credits:
description: Total credits as decimal string
example: '-5.00'
type: string
existing_mrc:
description: Total existing monthly recurring charges as decimal string
example: '100.00'
type: string
grand_total:
description: Grand total of all charges as decimal string
example: '180.00'
type: string
ledger_adjustments:
description: Ledger adjustments as decimal string
example: '0.00'
type: string
new_mrc:
description: Total new monthly recurring charges as decimal string
example: '50.00'
type: string
new_otc:
description: Total new one-time charges as decimal string
example: '25.00'
type: string
other:
description: Other charges as decimal string
example: '10.00'
type: string
required:
- new_mrc
- new_otc
- existing_mrc
- other
- credits
- ledger_adjustments
- grand_total
type: object
Summary:
example:
adjustments:
- amount: '-10.00'
description: Credit for service outage
event_date: '2025-05-15'
lines:
- alias: local
existing_this_month:
mrc: '20.00'
quantity: 8
name: Local DIDs
new_this_month:
mrc: '25.50'
otc: '5.00'
quantity: 10
type: comparative
- alias: port_out
amount: '15.75'
name: Port Out
quantity: 100
type: simple
properties:
adjustments:
description: List of billing adjustments
items:
$ref: '#/components/schemas/AdjustmentLine'
type: array
lines:
description: List of charge summary lines
items:
$ref: '#/components/schemas/SummaryLine'
type: array
required:
- lines
- adjustments
type: object
SummaryAndTotal:
properties:
currency:
description: Currency code
example: USD
type: string
end_date:
description: End date of the summary period
example: '2025-06-01'
format: date
type: string
start_date:
description: Start date of the summary period
example: '2025-05-01'
format: date
type: string
summary:
$ref: '#/components/schemas/Summary'
total:
$ref: '#/components/schemas/TotalSummary'
user_email:
description: User email address
example: user@example.com
format: email
type: string
user_id:
description: User identifier
example: 0db0b4aa-a83d-4d4f-ad9b-3ba7c1ac2ce8
type: string
required:
- user_id
- start_date
- end_date
- user_email
- currency
- summary
- total
type: object
MonthDetail:
properties:
mrc:
description: Monthly recurring charge amount as decimal string
example: '25.50'
type: string
otc:
description: One-time charge amount as decimal string
example: '5.00'
type:
- string
- 'null'
quantity:
description: Number of items
example: 10
type: integer
required:
- quantity
- mrc
type: object
SummaryLine:
discriminator:
propertyName: type
oneOf:
- $ref: '#/components/schemas/ComparativeLine'
- $ref: '#/components/schemas/SimpleLine'
SimpleLine:
properties:
alias:
description: Service alias
example: port_out
type: string
amount:
description: Total amount as decimal string
example: '15.75'
type: string
name:
description: Service name
example: Port Out
type: string
quantity:
description: Number of items
example: 100
type: integer
type:
enum:
- simple
example: simple
type: string
required:
- type
- name
- alias
- quantity
- amount
type: object
charges_Errors:
properties:
errors:
items:
$ref: '#/components/schemas/charges_Error'
type: array
ComparativeLine:
properties:
alias:
description: Service alias
example: local
type: string
existing_this_month:
$ref: '#/components/schemas/MonthDetail'
name:
description: Service name
example: Local DIDs
type: string
new_this_month:
$ref: '#/components/schemas/MonthDetail'
type:
enum:
- comparative
example: comparative
type: string
required:
- type
- name
- alias
- new_this_month
- existing_this_month
type: object
responses:
charges_BadRequestErrorResponse:
content:
application/json:
schema:
$ref: '#/components/schemas/charges_Errors'
description: Invalid request parameters or date range
charges_GenericErrorResponse:
content:
application/json:
schema:
$ref: '#/components/schemas/charges_Errors'
description: Unexpected error
charges_UnprocessableEntityErrorResponse:
content:
application/json:
schema:
$ref: '#/components/schemas/charges_Errors'
description: User account not found
charges_BadRequestErrorResponse_2:
description: Invalid request parameters or date range
content:
application/json:
schema:
$ref: '#/components/schemas/charges_Errors'
example:
errors:
- code: '10015'
title: Bad Request
detail: The request failed because it was not well-formed.
charges_GenericErrorResponse_2:
description: Unexpected error
content:
application/json:
schema:
$ref: '#/components/schemas/charges_Errors'
example:
errors:
- code: '10007'
title: Unexpected error
detail: An unexpected error occured.
charges_UnprocessableEntityErrorResponse_2:
description: User account not found
content:
application/json:
schema:
$ref: '#/components/schemas/charges_Errors'
example:
errors:
- code: '10027'
title: Unprocessable Entity
detail: The server understood the syntax of the request but was unable to process the instructions.
securitySchemes:
bearerAuth:
scheme: bearer
type: http
branded-calling_bearerAuth:
description: API key passed as a Bearer token in the Authorization header
scheme: bearer
type: http
oauthClientAuth:
description: OAuth 2.0 authentication for Telnyx API and MCP integrations
flows:
authorizationCode:
authorizationUrl: https://api.telnyx.com/v2/oauth/authorize
refreshUrl: https://api.telnyx.com/v2/oauth/token
scopes:
admin: Administrative access to Telnyx resources
tokenUrl: https://api.telnyx.com/v2/oauth/token
clientCredentials:
scopes:
admin: Administrative access to Telnyx resources
tokenUrl: https://api.telnyx.com/v2/oauth/token
type: oauth2
outbound-voice-profiles_bearerAuth:
bearerFormat: JWT
scheme: bearer
type: http
pronunciation-dicts_bearerAuth:
description: Telnyx API v2 key. Obtain from https://portal.telnyx.com
scheme: bearer
type: http
stored-payment-transactions_bearerAuth:
bearerFormat: JWT
scheme: bearer
type: http
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
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.
rcs-registration_bearerAuth:
type: http
scheme: bearer
bearerFormat: API key
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
x-refined-from:
- telnyx-openapi.yml
- telnyx-openapi.json