January 2023 Update
January 2023 cumulative update
✅ PHONE & EMAIL API - Facebook
The recently released Facebook Phone & Email API indicates if the phone number or the email address provided by the user has been found on Facebook.
The fields includes:
has_office_365: Indicates if the phone or the email address has been found on facebook
{
"resolution_id": "...",
"customer_id": "...",
"device_request_time": "...",
"webhook_url": "...",
"claims": [
"phone"
],
"value": "...",
...
"has_facebook": true
}{
"resolution_id": "...",
"customer_id": "...",
"device_request_time": "...",
"webhook_url": "...",
"claims": [
"email"
],
"value": "...",
...
"has_facebook": true
}⚠️ DEPRECATED: multiple API requests with the same customer_id
Removal date is scheduled for 2023-07-31
Our identity document was never meant to contain a history of changes in the customer touchpoints.
Even a single new touchpoint could have a significant impact on the digital score.
The change
In the API request, different touchpoint values will no longer be supported for the same customer_id.
For this reason, we're now enforcing a new customer ID whenever we detect a change in previously collected data. This applies to all input including:
- phone_number
- IP
- user_agent
We're still supporting the profile integration meaning that you can provide a new value if there was none before.
An example is providing a value for an email address during a multi-step signup process.
Will this impact my API integration?
This change is possibly breaking for your integration if:
- You make multiple API calls with the same customer_id
- You change a previously submitted value
How to mitigate this situation:
- If applicable don't update a previously submitted customer_id with new values, ideally you will generate a random customer ID for each new request.
- Whenever an update is necessary provide a new customer_id.