Feature

Session API for Temporary Number Masking

The Session API is the core number-masking primitive: send two real numbers and get back a virtual number that connects them in both directions. Routing is decided by who is calling, so the same number works whether Party A or Party B dials it. Sessions are idempotent on your own reference id (an order, ride or ticket id), so retries safely return the existing session instead of allocating a new number. Set an expiry so the number stops routing automatically once the order is done, cap the number of calls, or pause and resume routing at any time — all over a single REST endpoint.

Enterprise Ready

API Included

99.9% Uptime

Session API Benefits

What you get with Session API

Connect two numbers with one API call

Part of our Session API capability

Bidirectional — either party can dial the virtual number

Part of our Session API capability

Idempotent on your reference id (order/ride/ticket)

Part of our Session API capability

Auto-expire sessions after a set number of minutes

Part of our Session API capability

Cap calls per session, or pause and resume routing

Part of our Session API capability

Virtual number is freed for reuse when the session ends

Part of our Session API capability

Technical Specifications

Detailed specs for developers and technical teams

Endpoint

POST /masking/sessions

Auth

Bearer API key over HTTPS

Expiry

1 minute to 30 days, or no expiry

Idempotency

keyed on your reference id

Numbers

10-digit Indian mobiles (normalized)

Controls

extend, pause, resume, end (DELETE)

Use Cases

How businesses use Session API

Marketplace buyer-seller calls

Ride and delivery calls

Booking and appointment calls

Per-listing privacy

Industries Using Session API

Explore how different industries leverage this feature

Explore More Features

Other capabilities in our number masking solution

Session API FAQ

Ready to Use Session API?

Start using Session API in your application today. Free trial available.