info\@simpletelecom.com.au 1300 858 751

API Changelog

Every change to the Simple Telecom API in one place — the v1 REST baseline that runs today, and the platform integrations coming next: MCP server, personal access tokens, scopes and OAuth.

Get an API Token

Frequently Asked Questions

How do I find out when new API features ship?

Bookmark this page — it is the record of every API change. Launches are also announced by email to customers; if you have an integration planned, email info@simpletelecom.com.au and ask to be notified.

Is the current REST API changing?

No. The v1 REST API keeps working exactly as documented. The platform integrations (MCP, personal access tokens, scopes) are additive — new surfaces alongside the existing API.

What is coming next for the API?

The platform integrations release: an MCP server for AI assistants, scoped personal access tokens with a full lifecycle, a prepare-and-approve change model, and OAuth with PKCE for third-party apps. See the coming-soon entry below.

Will my existing token keep working?

Yes. Tokens you generate in the console today keep working. Personal access tokens are an additional, scoped model for the new platform surfaces.

Keep this page bookmarked: it is the single record of what changed in the Simple Telecom API and what ships next. Current entries first, upcoming work at the top of its own section.

Coming soon: platform integrations

The next release adds new surfaces alongside the current API — nothing below changes the existing v1 endpoints or your current tokens.

  • MCP server — connect AI assistants (Claude, Cursor, VS Code and other MCP-capable clients) to read call records, inspect configuration and prepare changes for human approval. Cancellation and payments are impossible by design. Details: the MCP server.
  • Personal access tokens — scoped, capped developer tokens with a one-time secret, atomic rotation and instant revocation, managed owner-only in the console. Details: personal access tokens.
  • Scopes and roles — a fixed scope list with viewer/operator/owner ceilings and a prepare → confirm approval model for every change. Details: scopes and permissions.
  • OAuth 2.0 with PKCE — the authorization flow for third-party apps: one-use codes, one-hour access tokens, rotating refresh tokens with family revocation.

Individual launch dates will be recorded here as each piece goes live.

2026-08: v1 REST API baseline

The current API, documented across the API overview:

  • Services — list active services and map service IDs to numbers (your services).
  • Call detail records — paginated rated call records per service (CDRs).
  • Routing — read a service's full forwarding configuration (call routing), add/update/remove forwarding numbers (manage forwarding), and enable or disable call recording (call recording).
  • Authentication — Bearer tokens generated in the customer console (authentication).
  • Errors & limits — a consistent JSON error model with machine-readable codes and rate-limit headers (error handling).
  • Reference — quickstart, code examples in curl/PHP/JavaScript, and end-to-end use cases.

Subscribing

Launch announcements go to customers by email, and this page is updated the day each feature goes live. Building something now? email us — we will flag you when the relevant surface launches.

Part of the Simple Telecom API.