Connect two people by phone through a temporary virtual number, so neither one sees the other's real number.
Numbers
02Live example
This is what number masking looks like when it lands on a customer’s phone.
Your driver Ramesh will call you from a masked number shortly to confirm your pickup location.
9:41✓
03The API call
One request. Copy it, drop in your key, and send.
curl https://api.msgbridge.in/v1/numbers/masking/bridge \ -H "Authorization: Bearer $API_KEY" \ -d party_a="+91XXXXXXXXXX" \ -d party_b="+91YYYYYYYYYY" \ -d ttl_minutes="60"04When to use it
- Connecting a delivery agent and a customer without sharing numbers
- Click-to-call from a website or app listing
- Cab and ride bookings
- Any two-sided marketplace that needs call privacy
05What's required
- A pool of virtual numbers for bridgingProvisioned during onboarding
- Time-based number mapping rulesConfigured once during integration
06How to go live
Define the mapping
Tell us how long a bridge should stay active — per order, per ride, or per session.
Integrate the API
Call the bridging endpoint whenever two parties need to be connected.
Go live
Numbers unmask automatically once the time-to-live expires, no manual cleanup needed.
07Related channels
08FAQ
No, both parties see a temporary virtual number; the real numbers are never exposed to each other.
The virtual number mapping stays active until its configured time-to-live expires, then it's released back into the pool.
Yes, call logs and duration are available over the API for support and dispute resolution.
Both — the same bridging works whether the call is initiated by dialling a number or by a click-to-call button on a website or app.
Ready to send with Number Masking?
Talk to us, or start building against the sandbox today.