Number Masking API
Welcome to our Number Masking documentation!
Overview
The Number masking service enables your users to connect in a phone call, while keeping their phone numbers private. By implementing Wavecell's Number Masking service, you can track all conversation metadata in your system while maintaining your customers' privacy.
The main advantages of number masking solutions are:
- Customer privacy
- In platform transactions
- Cost efficiency
This solution is ideal for the ridesharing, delivery or ecommerce industries where you want to connect your users without revealing any personal data. 8x8 Number Masking API allows you to configure a virtual or proxy number from your pool of numbers to receive call events, status call backs and respond with your preferred call flow function.
Prerequisites
Before you get started, please contact your account manager to ensure that your account has access to this product and that the following points have been managed:
- You will need a new sub-account id to enable and set up 8x8's Number Masking service
- In order to use our Number Masking API you require a Virtual Number that will be allocated to your sub-account by the 8x8 team
- You will need to provide an endpoint where the call handles will be sent to Once this is done, you can use our Number Masking product and start building your call flow.
If you haven't created your account yet, please go to the 8x8 website https://connect.8x8.com to sign up.
Number Masking flow
On the diagram below a simple number masking call diagram is shown:
Authentication
- HTTP: Bearer Auth
-
8x8 SMS API accepts an ApiKey Bearer Token authentication method.
-
You can generate tokens from your customer portal https://connect.8x8.com/
-
You need to include the following header in your requests:
Authorization: Bearer {apiKey}
Note: Replace the
{apiKey}placeholder with the key generated from the customer portal.
If you haven't created your account yet, please go to 8x8 website https://connect.8x8.com to sign up.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |