Developers · Masking API Swagger ReDoc Quickstart →

Masking API — Overview

Production base URL: https://api.cloudtalknet.com

CloudTalk Networks Masking lets your platform connect two people without exposing their real phone numbers. It's the privacy layer used by ride-hailing, delivery, marketplaces, recruiting — anywhere two parties need to talk briefly and then move on.

What you get

  • Privacy by default — neither party ever sees the other's real number
  • Flexible session windows — minutes, hours, or a full day per session
  • Concurrent sessions — many pairings active at once, each with its own masked number
  • Active-session routing — the same masked number can be reused safely across non-overlapping sessions
  • Single REST API — one auth header (X-API-Key), simple JSON payloads

How a call gets masked

When your app needs Customer A and Driver B to talk, you ask CloudTalk Networks for a session. We hand you a masked number valid for a window you choose (5 minutes, 2 hours, 24 hours — your call). Either party dials that number; we route the call to the other party's real number, end-to-end. When the session expires or you close it, the masked number returns to the pool.

sequenceDiagram
    autonumber
    participant Tenant as Your Platform
    participant CTN as CloudTalk Networks
    participant Cust as Customer
    participant Driver as Driver
    Tenant->>CTN: POST /v1/sessions { customer, driver, ttl }
    CTN-->>Tenant: { masked_e164, session_id, expires_at }
    Note over Cust,Driver: Both parties only ever see the masked number
    Cust->>CTN: dials masked_e164
    CTN->>Driver: bridges to driver's real number
    Driver-->>Cust: connected
    Note over CTN: TTL elapses or tenant closes session
    CTN->>CTN: masked number returns to pool

At a glance

flowchart LR
    A[Your Platform] -->|REST + X-API-Key| B(CloudTalk Networks)
    B --> C[(Masked-number pool)]
    B --> D[Active-session routing]
    B --> E[Telco network]
    E --> F((Real phone numbers))

What's next