| Version | Date | Summary |
|---|---|---|
| 0.0.16 | 2026-03-25 | New user (portal) to support third parties (e.g, Citizens Advice) operating a branded central portal |
| 0.0.15 | 2026-03-25 | Updated to allow other Data Users to reuse existing identity records from another Data User if the customer successfully re-identified themselves |
| 0.0.14 | 2026-03-24 | Downloadable and fully functional demo |
| 0.0.13 | 2026-03-24 | Support for sole, joint & multiple controllers |
| 0.0.12 | 2026-03-24 | Identity Records separated from Access Records. Re-identification via passkey and magic link added. POST /customer-sessions removed — Customer Portal accessed via direct URL with ir/mpxn parameter. |
| 0.0.11 | 2026-03-20 | Added DCC CoT endpoint and split /access-records into POST/PUT. |
| 0.0.10 | 2026-03-19 | Added Central Customer Portal design and redirect support. |
| 0.0.9 | 2026-03-18 | Added DCC interface for registering records discovered from their transaction log. |
| 0.0.8 | 2026-03-18 | Added EDP directory lookup (GET /data-users/{duid}) and webhook subscriptions for consent expiry and tenancy change events. |
| 0.0.7 | 2026-03-11 | Initial release. |
Documents
Change Log
History of changes
Last modified on March 25, 2026
Previous
Look Up Identity RecordsReturns Identity Records matching the supplied lookup parameters. Used by
a Data User to locate an existing record for a returning customer before
initiating re-identification.
At least one of `mpxn` or `email` must be supplied. Supplying both narrows
results to records where both values match.
Results are scoped to the authenticated Data User — a Data User cannot
look up records created by another Data User.
**Note on email lookup:** The register stores a one-way hash of the email
address for lookup purposes. The plaintext email is never returned in
responses. A match confirms a record exists for that address; the Data User
should already hold the email in their own system.
Next