Data Mapping & Payload

Purpose

This page shows the field mapping between the legacy and the new world, plus example payloads. It is meant to support the technical migration to the new User Data endpoint.

Overview

• Compare field names (Legacy → New) and semantics.
• Example JSON payloads (old/new).
• Links to the full field list and scope requirements.

Example payloads

Legacy (CReaM, test password example)

{
	"valid": "1",
	"uniquekey": "d902739aa663724bc660564563068164",
	"address_gender": "f",
	"address_name_title": "Dr.",
	"address_name_first": "Example_äöüß",
	"address_name_last": "Example_ÄÖÜ",
	"address_street": "Example Street",
	"address_postal_code": "50823",
	"address_city": "Köln",
	"address_country_id": "60",
	"address_country_iso": "CH",
	"occupation_profession_id": "1",
	"occupation_profession_parent_id": "1",
	"occupation_discipline_id": "1",
	"email": "deleted@doccheck.invalid"
}

New (DocCheck Access, test user example)

{    
	"unique_id": "50cf6446e3c757f9a43035c4e38d77c1",    
	"first_name": "Micha",    
	"last_name": "Muster",    
	"profession_id": 217,    
	"discipline_id": 274,    
	"activity_id": 100032,    
	"email": "testuser@example.com",    
	"street": "Test-Strasse 66",    
	"area_code": "55555",    
	"city": "Teststadt",    
	"country_id": 18,    
	"country_iso_code": "DE",    
	"user_language": "de"
}

Delta mapping (Legacy → New)

Legacy	New	Change	Note
uniquekey	unique_id	renamed	System scope; not shown in consent
email	email	unchanged
address_name_first	first_name	renamed
address_name_last	last_name	renamed
address_street	street	renamed
address_postal_code	area_code	renamed
address_city	city	renamed
address_country_iso	country_iso_code	renamed
address_country_id (ID mapping (opens new window))	country_id (ID mapping (opens new window))	renamed	type change string → integer
occupation_profession_id (ID mapping (opens new window))	profession_id (ID mapping (opens new window))	renamed / new IDs	The legacy_id corresponds to the code from the old system
occupation_discipline_id (ID mapping (opens new window))	discipline_id (ID mapping (opens new window))	renamed / new IDs	The legacy_id corresponds to the code from the old system
—	activity_id (ID mapping (opens new window))	new
—	user_language	new
occupation_profession_parent_id	—	removed	Parent id can be derived from mapping
address_gender	—	removed
address_name_title	—	removed

Scopes & return values

• Full field list including scope requirements: User data endpoint return values
• Consent & scopes notes: Personal & Consent (Migration)

Notes

• unique_id (from Economy) is selectable but not shown or consented in the consent form.

Next steps

1. Identify which legacy fields you currently use.
2. Apply the delta mapping in your systems (rename/remove/add).
3. Adjust scope configuration and test the new payload with test users.