Providing information related to a customer identity stored the account data bound to the customer's phone number.
Headers
authorization header for token
Correlation id for the different services
The API's Host value as defined in the RapidAPI Hub.
Request body
A public identifier addressing a telephone subscription. In mobile networks it corresponds to the MSISDN (Mobile Station International Subscriber Directory Number). In order to be globally unique it has to be formatted in international format, according to E.164 standard, prefixed with '+'.
Response
A public identifier addressing a telephone subscription. In mobile networks it corresponds to the MSISDN (Mobile Station International Subscriber Directory Number). In order to be globally unique it has to be formatted in international format, according to E.164 standard, prefixed with '+'.
Id number associated to the id_document of the customer stored on the Operator's system.
Type of the official identity document provided.
Expiration date of the identity document (ISO 8601).
Complete name of the customer stored on the Operator's system. It is usually composed of first/given name and last/family/sur- name in a country. Depending on the country, the order of first/give name and last/family/sur- name varies, and middle name could be included. It can use givenName, middleNames, familyName and/or familyNameAtBirth. For example, in ESP, name+familyName; in NLD, it can be name+middleNames+familyName or name+middleNames+familyNameAtBirth, etc.
First/given name or compound first/given name of the customer on the Operator's system.
Last name, family name, or surname of the customer stored on the Operator's system.
Complete name of the customer in Hankaku-Kana format (reading of name) for Japan, stored on the Operator's system.
Complete name of the customer in Zenkaku-Kana format (reading of name) for Japan, stored on the Operator's system.
Middle name/s of the customer stored on the Operator's system.
Last/family/sur- name at birth of the customer stored on the Operator's system.
Complete address of the customer stored on the Operator's system. For some countries, it is built following the usual concatenation of parameters in a country, but for other countries, this is not the case. For some countries, it can use streetName, streetNumber and/or houseNumberExtension. For example, in ESP, streetName+streetNumber; in NLD, it can be streetName+streetNumber or streetName+streetNumber+houseNumberExtension.
Name of the street of the customer's address on the Operator's system. It should not include the type of the street.
The street number of the customer's address on the Operator's system. Number identifying a specific property on the 'streetName'.
The postal code or Zip code of the customer's address, stored on the Operator's system.
Region/prefecture of the customer's address, stored on the Operator's system.
Locality of the customer's address, stored on the Operator's system.
Country of the customer's address stored on the Operator's system. Format ISO 3166-1 alpha-2.
House number extension of the customer stored on the Operator's system. Specific identifier of the house needed depending on the property type. For example, number of apartment in an apartment building.
Birthdate of the customer, in ISO 8601 calendar date format (YYYY-MM-DD), stored on the Operator's system.
Email address of the customer in the RFC specified format (local-part@domain), stored on the Operator's system.
Gender of the customer stored on the Operator's system (Male/Female/Other).
City where the customer was born.
Country where the customer was born. Format ISO 3166-1 alpha-2.
ISO 3166-1 alpha-2 code of the customer’s nationality. In the case a customer has more than one nationality, it is supposed to be the nationality related to the ID document provided in the match request.