generated: '2026-10-08'
method: searched
source: https://telnyx.com/openapi.json (servers, info.version, deprecated flags), https://developers.telnyx.com/docs/development/mcp/remote-mcp,
  https://github.com/team-telnyx/telnyx-mcp-server (README), https://status.telnyx.com/api/v2/status.json, https://telnyx.com/ai/sla.json,
  https://telnyx.com/release-notes; fetched 2026-10-08
versioning:
  scheme: URL path version
  current: v2
  base: https://api.telnyx.com/v2
  info_version: 2.0.0
  note: The published OpenAPI (info.version 2.0.0) describes v2 only; the team-telnyx/openapi repo still carries
    openapi/spec2.json for the earlier API. No versioning-policy page was found (docs/development/api-fundamentals/versioning.md
    answered 404). Capability JSON documents under /ai/*.json state a 90-day deprecation notice and in-response
    deprecation metadata for THOSE documents (https://telnyx.com/ai/capabilities.json schema_compatibility).
deprecation:
  policy_url: null
  headers: null
  note: 'No Sunset/Deprecation header policy is documented. Deprecations are announced in the OpenAPI (`deprecated:
    true` on the three operations below) and in product READMEs (the Python local MCP server is marked DEPRECATED
    in favour of npm telnyx-mcp; a ''legacy'' remote MCP page remains at /docs/development/mcp/remote-mcp/legacy).'
deprecated_operations:
- chat_public_chat_completions_post
- get_models_public_models_get
- chat_public_responses_completions_post
deprecated_products:
- product: team-telnyx/telnyx-mcp-server (Python local MCP server)
  replacement: npm telnyx-mcp (telnyx-node/packages/mcp-server)
  evidence: 'https://github.com/team-telnyx/telnyx-mcp-server README: "DEPRECATED: This Python-based MCP server
    is deprecated. Please migrate to the official TypeScript version"'
status_page: https://status.telnyx.com/
status_api: https://status.telnyx.com/api/v2/status.json
sla:
  url: https://telnyx.com/ai/sla.json
  uptime_guarantee: 99.99
  uptime_note: 99.99% uptime SLA for core voice and messaging services
  rpo_hours: 1
  rto_hours: 4
  credits:
  - downtime_threshold: < 99.99% uptime
    credit_percentage: 10
  - downtime_threshold: < 99.9% uptime
    credit_percentage: 25
  - downtime_threshold: < 99.0% uptime
    credit_percentage: 50
  measurement:
    method: Monthly uptime percentage calculated as (total minutes - downtime minutes) / total minutes × 100
    calculation_window: Monthly billing cycle
    excludes:
    - Scheduled maintenance windows (notified 72h in advance)
    - Force majeure events
    - Customer-caused outages
    - Internet routing issues beyond Telnyx network
changelog: https://telnyx.com/release-notes