The page you're currently viewing displays functionality for the SubscriberCheck API v0.2. If you want to see the functionality for the SubscriberCheck API v0.1, please click here
The tru.ID SubscriberCheck API confirms the ownership of a mobile phone number by verifying the possession of an active SIM card with the same number. It also provides a flag that indicates if the SIM card associated with the mobile phone number has changed within the last seven days.
SubscriberCheck combines the functionality offered by both PhoneCheck and SIMCheck into a single product. It works by creating a mobile data session to a unique Check URL for the purpose of phone number verification. tru.ID then resolves a match between the phone number that the mobile network operator identifies as the owner of the mobile data session and the phone number being verified. it also determines when the SIM card for the phone number was last changed for additional verification purposes.
This guide will walk you through a common approach to integrating SubscriberCheck workflow into a client/server architecture to achieve a match result, determine when SIM associated with the mobile phone number last changed and provide steps for integrating SubscriberCheck into your applications.
This guide will be using four different entities. These are:
- Customer's device, the mobile device of the person attempting to verify they're the owner of that phone number.
- Your Backend Server is the server the customer's device communicates with for the application to run.
- tru.ID API is the API your integration needs to communicate with for the SubscriberCheck to succeed.
- Mobile Network Operator (MNO) is the mobile provider that provides your Customer's SIM card.
SubscriberCheck Workflow Integration
The SubscriberCheck workflow consists of three sections.
- Create the SubscriberCheck - Initializing the SubscriberCheck process.
- Process the SubscriberCheck - Accessing the SubscriberCheck's
check_urlover a mobile data connection.
- Complete the SubscriberCheck - Submitting the SubscriberCheck's
codeand verifying the Check has been completed.
1) Create a SubscriberCheck
Creating a SubscriberCheck workflow is as follows:
- Customer sends phone number to Backend Server.
- Backend server sends a
POSTrequest to tru.ID SubscriberCheck API.
- tru.ID SubscriberCheck API returns a response with the
check_idand a unique
- Backend server returns the
check_urlto the application.
Once the device application has received the user's phone number, send it to your backend server.
Device sends Phone Number to your Backend Server
Backend Server creates a SubscriberCheck with tru.ID's API
Backend Server returns the Check URL to the Device
2) Process the SubscriberCheck
Processing a SubscriberCheck workflow is as follows:
- Customer application opens the tru.ID Check URL
- Customer Device follows redirect URL to MNO
- 200 Response returned including
codeor an error message depending on the result.
- 200 Response returned including
Device opens the tru.ID Check URL
3) Complete the SubscriberCheck
Completing a SubscriberCheck workflow is as follows:
- Device passes
codeto the backend server.
- Server makes a
PATCHrequest to tru.ID with
- Verification result returned to the device, including SIM changed status.
- SubscriberCheck is now complete.
Device passes 'code' to the Backend Server
Backend Server makes 'PATCH' request to tru.ID SubscriberCheck API
tru.ID SubscriberCheck API returns 'PATCH' result to Backend Server
Get Started with development
There are multiple SDKs created by tru.ID to help developers integrate the APIs into their mobile application and backend server with minimal effort. To support these SDKs, guides have been written on getting started with the mobile technology of your choosing, whether it be iOS, Android, Flutter, and many others.
To get started with the mobile technology of your choice, click on the getting started with link.