Overview
Additional Information
Overview
Additional Information
Overview
Additional Information
Overview
Additional Information
Overview
Additional Information
Number Recycling
The API can be used to check whether the subscriber of the phone number has changed.
A common scenario is when an Application Service Provider (ASP) wants to check whether there has been a change in the user associated with the phone number after the specified date. This allows the ASP to ensure that a phone number is correctly linked to an user and prevent the mis-delivery of SMS messages.
It can be used for
Verify that a phone number still belongs to the same user.
Prevent SMS and notification delivery to the wrong recipient.
Reduce fraud caused by recycled phone numbers.
Improve customer identity and account verification processes
API Information
Version | v0.2.0 |
Protocol | HTTPS |
Sandbox URL | https://api-sandbox.vf-dmp.engineering.vodafone.com |
Live URL | https://api.vf-dmp.engineering.vodafone.com |
Version history | Release date | Status | Description |
|---|---|---|---|
0.2 | September 2025 | Live | This API checks whether a phone number has been reassigned to a different subscriber since a specified date, helping prevent fraud and misdirected communications. |
Endpoints
Method | Name | Endpoint |
|---|---|---|
POST | Get Access Token Using JWT Bearer | /oauth2/v2/token |
POST | Authentication Request | /openIDConnectCIBA/v1/bc-authorize |
POST | Token Request | /openIDConnectCIBA/v1/token |
POST | Check Number Recycling | /number-recycling/v0.2.0/check |
GET | Ping | /number-recycling/v0.2.0/ping |
How it works
The Service Provider sends a request to the Number Recycling API, containing the customer's MSISDN and a specified date.
The API checks Vodafone's records to determine whether the subscriber associated with that phone number has changed after the specified date.
If the phone number is still associated with the same subscriber, the API returns phoneNumberRecycled: false.
If the phone number has been reassigned to a different subscriber since the specified date, the API returns phoneNumberRecycled: true.
The Service Provider can use this information to decide whether it is safe to send SMS messages, perform identity verification, or continue other customer communications.
Billing Rule
A billable event occurs when the service returns an HTTP 200 OK response.
Run in Postman
To begin using the Vodafone workspace in Postman, please follow the steps below to create a set of credentials that can be used with our sandbox collections:
Register an account on https://developer.vodafone.com and create a sandbox app for the APIs that you are interested in.
Use the Client Key and Secret from your sandbox app to populate the relating variables in the "Sandbox Credentials" environment group in Postman.
These API use a three-legged OAuth flow. A three-legged OAuth process involves three parties: the end-user (or resource owner), the client (the third-party application), and the server (or authorization server).
First call the authorize endpoint to get an authorization code. Your client credentials will be taken from the environment variables.
You need to call the authorize end-point for each Identity API in the CAMARA portfolio as the product scope is set in the request body of the authorize call.
Call the token endpoint to exchange the authorization code for a bearer token that is used in the API resource endpoint.
The last bearer token and trace ID will be stored in collection variables associated with the API solution that you have chosen.
You can use these collections as read-only or create a fork into your own personal workspace to edit the details.
You can access all of Vodafone's sandbox APIs in our Postman workspace by clicking the link below:
What is Postman?
Postman is a popular development and testing tool that is widely used across the API developer community. It offers an easy to use interface for making HTTP requests, testing API responses and collaborating with team members. For more details, see postman.com.