# User Data Endpoint Return Values

The following values may be returned by the User Data Endpoint if the user has given consent and the respective data is available. If a value has no data, it will be returned as 0 or an empty string.

String values are HTML‑encoded (Köln for "Köln") to prevent encoding issues. Characters outside the ASCII range may not be included.

unique_id (system scope)

  • unique_id is selectable starting with the Economy license.
  • It is not displayed in the consent form nor explicitly consented; no separate consent is required.
  • The unique_id is provided system‑side and is available from the endpoint after successful login.
Property Scope Type Short description License
Economy
unique_id unique_id string (50), lowercase Unique DocCheck identifier Economy
country_id country integer Country (ID), ID Mapping (opens new window) Economy
user_language language string Language Economy
profession_id profession integer Profession (ID), ID Mapping (opens new window) Economy
Business
area_code address string Address Business
street address string Address Business
city address string Address Business
discipline_id occupation_detail integer Occupation detail (ID), ID Mapping (opens new window) Business
activity_id occupation_detail integer Occupation detail (ID), ID Mapping (opens new window) Business
email email string Email address Business
first_name name string First name Business
last_name name string Last name Business

# ID Mapping Details

# Syntax

# professions, disciplines & activities:

{"id":integer,"name":"string","parent_id":integer,"legacy_id":integer}

# countries:

{"id":integer,"name":"string","iso":"string"}

Note

  • legacy_id corresponds to the historical code used in the legacy lists and helps migrate/map existing data to the new lists (details and examples: Data Mapping & Payload).
  • id and parent_id can be identical when a category also acts as a top‑level group (root node). Example (Activities): id=100009 “Practice – owner” with parent_id=100009. In most other cases, top‑level nodes use parent_id=0.