Identification to the operator without user consent
The response is a JSON whose keys are defined below:
Key | Description | Format |
family_name | Result of the comparison on the last name | NUMBER |
gender | Result of the comparison on civility | NUMBER |
birthdate | Result of the comparison on the date of birth | NUMBER |
given_name | Result of the comparison on the first name | NUMBER |
address | Contains all the keys described in the following table | JSON OBJECT |
Result of the comparison on the email address | NUMBER |
Elements of the “address” key :
Key | Description | Format |
country | Result of the comparison on the country | STRING(3) |
postal_code | Result of the comparison on the postal code | STRING(3) |
street_address | Result of the comparison on the street | STRING(3) |
locality | Result of the comparison on the city | STRING(3) |
Response example for « matching_notp » scope:
{
"family_name": 1.0,
"gender": "",
"birthdate": 1.0,
"given_name": 1.0,
"address": {
"country": 1.0,
"postal_code": 0.78,
"street_address": 0.56,
"locality": 0.44
},
"email": 1.0
}
Identification to the operator with user consent
The response is a JSON whose keys are defined below:
Key | Description | Format |
status | « success » | STRING |
operator | Operator | STRING |
url | URL of the Operator API | STRING |
Response example:
{
"status": "success",
"operator": "Orange",
"url": "https://api.operator /openidconnect/fr"
}