Look Up a Data User by DUID

Returns profile and status information for a registered Data User organisation identified by DUID.

Intended caller: Data Providers.

When a Data Provider calls GET /access-records/{ak} to verify an access record, the response includes a duid identifying the organisation that registered the record. Without this endpoint, the Data Provider has no independent means to confirm that the duid belongs to an active, known organisation — they can only rely on their own bilateral onboarding records.

This endpoint closes that gap by providing a central directory lookup. Data Providers should call this endpoint as part of first-time onboarding of a new DUID encountered in a verification response, and may call it periodically to detect status changes (e.g. suspension).

Authentication: Bearer token required. Data Providers must obtain a token via GET /auth/token using their own account_id:secret_key credentials, which are provisioned separately from Data User credentials.

Note on DUID mapping: The register intentionally does not map DUIDs to Data Provider platform account IDs — that linkage is the Data Provider’s responsibility, as stated in the GET /access-records/{ak} verification checklist. This endpoint supplies the canonical human-readable identity (name, status, contact) for the DUID so the Data Provider can confirm the mapping is correct on their side.