List Access Records for a Meter Point
Returns all Access Records and Discovered Records for a given meter point.
Role: data_user — scoped to MPxNs the caller has a registered Access Record for (any state). Returns 403 if the caller has no record for the requested MPxN. This prevents Data Users from querying arbitrary meter points.
Role: portal — can query any MPxN, but must supply a confirmed reidentification-token as a query parameter. The token proves the customer is present and has consented to the lookup. Obtain the token via POST /identity-records/reidentify. The token is consumed on use.
To allow customers to view all access records across all Data Users, Data Users should redirect customers to the Central Customer Portal rather than calling this endpoint themselves.
Documentation Index
Fetch the complete documentation index at: https://docs.auth.energy/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
JWT from GET /auth/token. Pass as Authorization: Bearer <token>. Expires after 7200s.
Path Parameters
Meter Point Administration Number (MPAN) or Meter Point Reference Number (MPRN).
^(?:[0-9A-HJ-NPR-Z]{2}[0-9]{8,10}|[0-9]{10})$"1234567890123"
Query Parameters
Filter by record lifecycle state. Omit to return all states. Lifecycle state of the access record.
ACTIVE— access is registered and in force.EXPIRED— the record'sexpiryhas passed.REVOKED— the Controller has removed their registration, or the customer has withdrawn consent. Retained for audit withaccess-event.revoked-atset.DISCOVERED— a sparse record created by the DCC from historic meter transaction logs. The organisation has not yet registered as a Data User. Visible to customers for transparency but cannot authorise data release. Transitions to superseded when the organisation registers a full record.
ACTIVE, EXPIRED, REVOKED, DISCOVERED Filter by legal basis. Omit to return all bases. The legal basis under which the Controller accesses customer data.
Consent bases — notice and access-event.consent must be populated.
| Value | Plain name | Article |
|---|---|---|
uk-consent | UK Consent | UK GDPR Art. 6(1)(a) |
uk-explicit-consent | UK Explicit Consent | UK GDPR Art. 9(2)(a) |
Non-consent bases — notice and access-event.consent must be null.
| Value | Plain name | Article | Supporting field (on lead controller) |
|---|---|---|---|
uk-legitimate-interests | UK Legitimate Interests | UK GDPR Art. 6(1)(f) | lia-reference |
uk-public-task | UK Public Task | UK GDPR Art. 6(1)(e) | statutory-reference |
uk-legal-obligation | UK Legal Obligation | UK GDPR Art. 6(1)(c) | statutory-reference |
uk-contract | UK Contract | UK GDPR Art. 6(1)(b) | — |
uk-consent, uk-explicit-consent, uk-legitimate-interests, uk-public-task, uk-legal-obligation, uk-contract "uk-consent"
Required for portal role accounts. A confirmed token-ref obtained via POST /identity-records/reidentify. Proves the customer is present. Consumed on use — a new token is required for each portal session.

