Skip to main content
POST
/
discovered-access
Submit a Discovered Access Record
curl --request POST \
  --url https://api.central.consent/v1/discovered-access \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "mpxn": "1234567890123",
  "organisation-name": "Acme Energy Services Ltd",
  "organisation-reference": "org_abc123def456",
  "first-seen": "2024-06-01",
  "last-seen": "2026-02-28",
  "data-types-observed": [
    "HH-CONSUMPTION"
  ],
  "source-reference": "DCC-TX-LOG-2026-03-001"
}
'
{
  "response": {
    "resource": "/v1/access-records/ak_691df0c788ca043403b7fa90",
    "timestamp": "2026-03-11T12:00:00Z",
    "transaction-id": "tid_691df0c788ca043403b7fa90"
  },
  "ak": "ak_691df0c788ca043403b7fa90",
  "state": "ACTIVE"
}

Authorizations

​
Authorization
string
header
required

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

Body

application/json

A sparse access record derived from DCC historic meter transaction logs. Submitted by the DCC when it detects an organisation making data requests against a meter point that has no corresponding DAR registration.

This schema is intentionally minimal — it captures only what the DCC can observe from transaction logs without requiring the organisation's participation. The organisation-name is the DCC's own record of the requesting party; it is not validated against any external directory.

DISCOVERED records are visible to customers in the access record list and serve as a prompt for the organisation to formalise their registration. They cannot be used to authorise data release.

​
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"

​
organisation-name
string
required

The name of the organisation as known to the DCC from its transaction records. Not validated against the Data User directory.

Maximum string length: 255
Example:

"Acme Energy Services Ltd"

​
organisation-reference
string
required

The DCC's internal identifier for this organisation. Used to link the DISCOVERED record to a full access record when the organisation subsequently registers as a Data User.

Maximum string length: 255
Example:

"org_abc123def456"

​
first-seen
string<date>
required

The earliest date on which the DCC observed a data request from this organisation against this MPxN.

Example:

"2024-06-01"

​
data-types-observed
enum<string>[]
required

The data types the DCC observed being requested. Uses the same enum as processing.data-types on a full access record.

Minimum array length: 1
Available options:
HH-CONSUMPTION,
HH-EXPORT,
MTH-CONSUMPTION,
MTH-EXPORT,
ANNUAL-CONSUMPTION,
ANNUAL-EXPORT,
TARIFF-IMPORT,
TARIFF-EXPORT
​
source-reference
string
required

The DCC's internal reference for the transaction log batch or audit record from which this discovered access was derived. Retained for traceability.

Maximum string length: 255
Example:

"DCC-TX-LOG-2026-03-001"

​
last-seen
string<date>

The most recent date on which the DCC observed a data request from this organisation against this MPxN.

Example:

"2026-02-28"

Response

Existing discovered access record updated (same mpxn and organisation-reference already present).

​
response
object
required
​
ak
string
required

Unique opaque identifier for an access record, issued by the register on creation. Treat as a secret — possession enables access verification.

Pattern: ^ak_[0-9a-f]{24}$
Example:

"ak_691df0c788ca043403b7fa90"

​
state
enum<string>
required

Will always be DISCOVERED for records created by this endpoint.

Available options:
ACTIVE,
EXPIRED,
REVOKED,
DISCOVERED
Last modified on March 25, 2026