v1

latestOpenAPI 3.0.02026-07-1427437.7 KB

Profiles

Get unmasked profile

Retrieves unmasked information of a specific client, by its profileId.

Since your store's profile schema is customizable, the schema and examples presented below may differ from yours. Your integration must be adapted accordingly.

Learn more about the Profile System and its other API endpoints.

get/api/storage/profile-system/profiles/{profileId}/unmask

Path parameters

profileIdstring required

Example:70caf394-8534-447e-a0ca-1803c669c771

ID of the client's profile as returned by the Create profile endpoint's response, in the id field. It can also be an alternativeKey according to your custom profile schema. In this case, this request should also send the alternativeKey parameter.

Query parameters

reasonstring required

Example:data-validation

Reason for requesting unmasked data.

alternativeKeystring

Example:email

The profileId path parameter may be substituted by other profile fields in this request. When making this request, send the alternativeKey parameter with a value equal to the key of the field you wish to use as profileId.

Currently, there are two possible values for this parameter: email and document.

Headers

Content-Typestring required

Example:application/json

Type of the content being sent.

Acceptstring required

Example:application/json

HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.

Response

{"stackTrail":"paths:/api/storage/profile-system/profiles/{profileId}/unmask:get:responses:200:content:application/json:schema:items","oasType":"schema","type":"unknown"}