Telecom X developer platform

Got an idea?
Build it on real telephony.

Phone numbers, mobile subscriptions, hosted PBX, SIP trunks, internet and TV. Telecom X runs all of it for Danish businesses, and every part is open to you through one REST/JSON API with realtime events. No other Danish operator gives developers this much access.

Explore the API Get started

1,250+public documentation pages
45+API areas, from PBX to mobile and TV
Realtimecall, PBX and config events pushed to your app
1 APIthe same one behind our own portals and apps

What will you build?

Explore the API

Every area works the same way: log in once, then call plain JSON endpoints with your token. Pick a starting point.

Telephony & PBX

450+ pages

Hosted PBX, SIP trunks, phone numbers, porting, routing and call records.

TV & streaming

280 pages

Channels, EPG, packages, recordings, set-top boxes and app clients.

Customers & billing

160+ pages

Customers, users, products, invoices, help center and third-party integrations.

Platform & tools

100+ pages

Authentication, the error format, search, files, logs and a toolbox of utilities.

Mobile

80+ pages

Mobile subscriptions on TDC and Telenor, SIM cards, roaming and usage.

Healthcare

80 pages

Flexcare: video calls, tablets, set-top boxes and device management for care.

Internet & network

70+ pages

Fiber and xDSL, 5G routers and other network devices, DNS and ZeroTier.

Messaging

20+ pages

Send SMS, manage mailboxes, and brand your e-mail, SMS and PDF templates.

AI & voice

18 pages

Text-to-speech, speech-to-text, voices, AI usage and quotas.

See all API areas →

Get started

  1. Get accessAlready a Telecom X customer or reseller? Use the login you have. New here? Write to info@telecomx.dk or call 70 30 50 50 and tell us what you want to build.
  2. Log in, get a tokenOne call to /auth/login returns a token. It stays valid while you use it; see Authentication for long-lived and read-only tokens.
  3. Call any endpointSend the token as Authorization: Bearer. Every reply is JSON, and errors always come back in the same format.
  4. Go realtimeConnect a socket.io client to realtime.telecomx.dk with the same token and subscribe to call, PBX and config events.
# Log in. The reply contains a token.
curl -s https://api.telecomx.dk/auth/login \
  -H 'Content-Type: application/json' \
  -d '{"username": "you@example.com", "password": "your password"}'
 
# Use the token on every request.
curl -s https://api.telecomx.dk/ping -H 'Authorization: Bearer <token>'

Let your AI assistant read the docs

The whole wiki is available over the Model Context Protocol at https://wiki.telecomx.dk/mcp. Connect Claude, Cursor or any other MCP-capable client, and ask it to find the right endpoint, read the reference and write the integration with you.

Claude Code:

claude mcp add --transport http telecomx-wiki https://wiki.telecomx.dk/mcp

Claude Desktop (in claude_desktop_config.json, requires Node.js):

{
  "mcpServers": {
    "telecomx-wiki": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://wiki.telecomx.dk/mcp"]
    }
  }
}

Good to know

Have an idea? Let's build it together.

Tell us what you want to make. We will give you a technical walkthrough of the platform and get you set up.

info@telecomx.dk 70 30 50 50

Found a mistake in the docs, or missing something? Write to pm@telecomx.dk.  ·