MSISDN Retrieval V2
Alacrity provides a method for you to retrieve the customer's MSISDN via header enrichment (if it is available). Permission to use MSISDN Retrieval via HE (Header Enrichment) needs to be provided by the operator.
This is a two step process:
- Redirect the user to Alacrity where we will attempt to obtain the MSISDN.
- Retrieve the MSISDN via the API.
Redirect
Request
Redirect the customer to:
http://msisdn.sla-alacrity.com/msisdn_retrieval/v2/msisdn/redirect?redirect_url={redirect_url}&merchant={merchant}&service={service}&transaction_id={transaction_id}
Parameters
| Name | Description | Type | Usage |
|---|---|---|---|
| redirect_url | Your URL that we redirect the end customer back to after msisdn detection. | string | mandatory |
| merchant | The Alacrity merchant URI that identifies which merchant this transaction belongs to. | string | mandatory |
| service | The Alacrity service URI that identifies the service that this transaction belongs to. | string | mandatory |
| transaction_id | A unique transaction ID generated by you. | integer | mandatory |
If any of the above parameters are missing you will receive a 400 Bad Request
Success
If the MSISDN is successfully detected and saved you will receive the following via redirect:
http://your-redirect-url?status=success&transaction_id={transaction_id}
Errors
Other errors will be returned to your redirect URL and will have the following format:
http://your-redirect-url/?status=error&transaction_id={transaction_id}&message={reason_for_the_error}
MSISDN Retrieval
Retrieve MSISDN for specific transaction
Request
GET /msisdn_retrieval/v2/msisdn/retrieve?transaction_id={ID}&merchant={merchant}&service={service}
Request Parameters
| Name | Description | Type | Usage |
|---|---|---|---|
| transaction_id | A unique identifier to the current transaction. This value will be used to retrieve the MSISDN. This is the transaction id used in the re-direct call above. | string | mandatory |
| merchant | The Alacrity merchant URI that identifies which merchant this transaction belongs to. | string | mandatory |
| service | The Alacrity service URI that identifies the service that this transaction belongs to. | string | mandatory |
GET /amsisdn_retrieval/v2/msisdn/retrieve?transaction_id=19235&
merchant=partner:1b0a715f-27c5-46c2-9e97-00748dca334f
&service=campaign:56yhws-87e376-yuio43-45yhh7 HTTP/1.1
Host: msisdn.sla-alacrity.com
Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==
Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
{
"msisdn_protection":{
"msisdn": "tel:353867676767"
}
}
HTTP/1.1 410 Gone
Response Codes
| Response Code | Description |
|---|---|
| 200 | Success. |
| 400 | Bad Request. |
| 401 | Unauthorized. Credentials are invalid or the campaign is not approved. |
| 410 | Record has not been found for the parameters supplied or the MSISDN has already been accessed. |
| 500 | An error has occurred. |
Warning
Each combination of transaction ID / MSISDN will only be retrievable once.
Info
Please note that a customer's MSISDN is encrypted in SLA Digital’s database and is only decrypted when requested by the Merchant.
Please note that for certain Operators Merchants will receive either a MSISDN or an ACR.For Telenor Operators (Digi, Myanmar) the Merchant will receive an ACR. For each time the Merchant tries to retrieve a MSISDN for the same user they will get a new ACR. You can identify that those ACRs belong to a single user by validating the first 30 characters of the ACR.
Updated about 1 year ago