Ride-hailing
Connect riders and drivers without revealing real numbers, using a temporary proxy for each trip.
Illustrative
Feature · Number masking
Let two people talk, without sharing numbers.
Acepeak number masking connects riders, drivers or buyers on a call through a temporary proxy number, so nobody’s real number is revealed. It is part of the Voice API.
Temporary proxy numberVoice APIREST sessionYour brand
One masked call, live
Rider+44 ••• 123Hidden
Proxy+44 20 7946 0000
Driver+44 ••• 987Hidden
Rider dials the proxy…Proxy forwards the callDriver answers · numbers stay hidden
Illustrative numbers
Every ride, delivery and marketplace order ends with two strangers who need to talk. Masking lets them, and keeps both numbers private.
How it works
One session, one proxy per trip or order.
- 1
Create a session
One call to the Voice API starts a masking session.
POST /v1/masking/sessions - 2
A proxy is assigned
A temporary proxy number is assigned for that trip or order.
proxy: assigned - 3
Both sides call it
Each person reaches the other through the proxy number.
caller → proxy - 4
The call connects
The two parties talk and neither real number is revealed.
numbers: hidden
Where it is used
Anywhere two people meet through your app.
Delivery
Couriers and recipients reach each other during the drop-off, without trading numbers.
See logistics solutionsMarketplaces
Buyers and sellers talk about an order through a proxy, not a personal number.
Support on the phone
Let a customer and a team member speak without either side exposing a private line.
What each side sees
The proxy in front, real numbers behind.
| Who | Sees | Kept private |
|---|---|---|
| The rider or buyer | The proxy number | Their own number and the other side’s |
| The driver or seller | The proxy number | Their own number and the other side’s |
| Your platform | The masking session it created | Nothing: both real numbers stay in your system |
Part of the Voice API
One endpoint, next to the rest of voice.
Masking is one call in the Voice API. It runs under your brand and domain, on your own switch and routes.
POST
/v1/callsCall controlMake, answer, transfer, hold and bridge calls.PUT
/v1/ivr/{id}Visual IVR builderDesign menus without writing code.POST
/v1/conferencesConferencingHost multi-party calls with moderator controls.GET
/v1/calls/{id}/recordingCall recordingRecord calls on demand and fetch the files.POST
/v1/masking/sessionsNumber maskingConnect two parties without revealing real numbers.POST
/v1/click-to-callClick-to-callStart a call from a website button.Endpoints as listed for the Voice API.
FAQ
Number masking, answered.
Number masking connects two parties on a call without revealing their real phone numbers. Each side calls and receives through a temporary proxy number instead.
Marketplaces, ride-hailing and delivery apps. It connects riders, drivers or buyers without revealing anyone’s real number.
Through the Voice API. You create a masking session with POST /v1/masking/sessions and a proxy number is assigned for that session.
Yes. It sits in the Voice API next to call control, the IVR builder, conferencing, recording and click-to-call.
Yes. The API, docs and portal run under your brand and domain, on your own switch and routes.
Keep every number private.
Talk to partnerships about number masking in the Voice API, under your own brand.