Skip to main content
GET
/
identity-records
/
exists
Check Identity Record Existence by MPxN
curl --request GET \
  --url https://api.central.consent/v1/identity-records/exists \
  --header 'Authorization: Bearer <token>'
{
  "response": {
    "resource": "/v1/access-records/ak_691df0c788ca043403b7fa90",
    "timestamp": "2026-03-11T12:00:00Z",
    "transaction-id": "tid_691df0c788ca043403b7fa90"
  },
  "mpxn": "1234567890123",
  "exists": true,
  "available-methods": [
    "magic-link"
  ]
}

Authorizations

​
Authorization
string
header
required

JWT from GET /auth/token. Pass as Authorization: Bearer <token>. Expires after 7200s.

Query Parameters

​
mpxn
string
required

Meter Point Administration Number (MPAN) or Meter Point Reference Number (MPRN).

Pattern: ^(?:[0-9A-HJ-NPR-Z]{2}[0-9]{8,10}|[0-9]{10})$
Example:

"1234567890123"

Response

Existence check result including available re-identification methods.

​
response
object
required
​
mpxn
string
required

Meter Point Administration Number (MPAN) or Meter Point Reference Number (MPRN).

Pattern: ^(?:[0-9A-HJ-NPR-Z]{2}[0-9]{8,10}|[0-9]{10})$
Example:

"1234567890123"

​
exists
boolean
required
​
available-methods
enum<string>[]
required

Re-identification methods available for this MPxN. Empty when exists is false. Possible values: passkey-assert (credentials registered), magic-link (email stored), passkey-register (always present — a new passkey can always be enrolled).

The re-identification method to use.

magic-link — single-step. The register dispatches a signed link to the stored email address. Optionally supply redirect-url to send the customer back to the Data User's app after clicking; otherwise the customer lands on central.consent. Poll or check GET /identity-records/{ir}/re-identify/{token-ref} to confirm.

passkey-assert — two-step redirect. The response contains a passkey-redirect with a short-lived URL to id.central.consent. Redirect the customer there; the register runs the WebAuthn assertion against the stored public key on its own origin, then redirects back with ?dar-passkey-token={token-ref}. Call GET /identity-records/{ir}/re-identify/{token-ref} once to confirm.

passkey-register — two-step redirect for new device enrolment. Same flow as passkey-assert but runs a registration ceremony instead of assertion. Stores a new public key credential on the Identity Record and confirms re-identification on success.

Available options:
magic-link,
passkey-assert,
passkey-register
Last modified on March 25, 2026