> ## 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. # Submit a Change of Tenancy Event > Records a Change of Tenancy (CoT) against an MPxN and triggers `tenancy.change` webhooks to all Data Users with one or more `ACTIVE` access records on that MPxN. **Authentication:** Restricted to DCC system credentials. Standard Data User bearer tokens are rejected on this endpoint with `403`. **What the register does on receipt:** 1. Records the CoT event for audit with the MPxN, effective date, and DCC source reference. 2. Identifies all `ACTIVE` access records for the MPxN across all registered Data Users. 3. Fires a `tenancy.change` webhook to each affected Data User, including the `affected-aks` array so Data Users can perform targeted revocations without a separate list query. 4. Returns a summary of Data Users notified and records affected. **What the register does NOT do:** Automatically revoke access records. Revocation is the Controller's responsibility on receipt of the webhook. CoT events from the DCC can occasionally be false alerts; Controllers should verify before revoking records with non-occupancy legal bases (e.g. `uk-public-task`, `uk-legitimate-interests`). **Idempotency:** Submitting the same `mpxn` + `effective-date` + `source-reference` returns `200` and does not re-fire webhooks. **PII:** The payload contains only the MPxN and the effective date. No new occupant name, address, or contact details are included. ## OpenAPI ````yaml /data-access-register/api/openapi-dar.yaml post /cot-events openapi: 3.1.0 info: title: Data Access Register description: > Core APIs for the Central Data Access Register. The register records all lawful access to customer energy data by Controllers, regardless of the legal basis on which that access rests. It is not exclusively a consent register — legitimate interests, public task, legal obligation, and contract are all within scope alongside consent-based access. **Jurisdiction:** This is a UK-only solution. All Controllers, customers, and meter points are within Great Britain. The governing data protection framework is **UK GDPR** and the **Data Protection Act 2018**. EU GDPR does not apply. The jurisdiction field is fixed to `GB` and does not need to be supplied. ## Purpose The register provides a single, auditable source of truth for: - **Controllers** — to record and demonstrate the legal basis under which they access customer meter data. - **Data Providers** — to verify that a Controller has a registered, active access record before releasing data. - **Customers** — to view all parties registered as having lawful access to their meter point, on request via any Controller. ## Party Model | Party | UK GDPR Role | Description | |---|---|---| | **Data User** | Processor | Operates the register. Fetches and processes meter data on behalf of Controllers. Authenticated via bearer token. | | **Controller** | Data Controller | A B2B customer of the Data User. One or more Controllers may be registered per access record — sole, joint (Art. 26), or group (trading name transparency). Bears GDPR accountability for the legal basis and its ongoing validity. | | **Customer** | Data Subject | The energy customer. Identified by MPxN to minimise PII held centrally. | | **Data Provider** | Data Source | Holds meter data. Verifies access records before releasing data via `GET /access-records/{ak}`. | ## Record Structure All access records share a single schema — `AccessRecord` — with four sections aligned to ISO/IEC TS 27560:2023: 1. **`record-metadata`** — record identifier, creation timestamp, controller arrangement (sole, joint, or group), and a reference to the associated Identity Record. Present for all records. 2. **`notice`** — the privacy notice(s) presented to the customer. Present only for consent-based records; null for all other legal bases. Supports a single shared notice (common) or per-controller notices (joint arrangements where controllers discharge Art. 13 obligations separately). 3. **`processing`** — legal basis, purpose, data types, and related obligations. Present for all records. Per-controller compliance fields (privacy rights URL, LIA reference, statutory reference, storage conditions) are held on each controller entry within `record-metadata.controller-arrangement`. 4. **`access-event`** — when and how access was registered or consent was obtained; current lifecycle state. Present for all records. The `notice` and `access-event.consent` sub-object are null for non-consent records. The `access-event.consent` sub-object is null for non-consent records and populated for consent records. ## Identity Records The person-property relationship — who the individual is and their occupancy of the meter point — is held separately in an **Identity Record** (`/identity-records`). This keeps PII (MPxN, address, move-in date) and identity verification evidence out of the access record entirely. Each `AccessRecord` carries an `identity-record-ref` (`ir` key) linking it to its Identity Record. Identity Records are accessible only to authenticated Data Users. The unauthenticated `GET /access-records/{ak}` endpoint used by Data Providers never returns PII. Identity Records support two re-identification flows to reconnect a returning customer to an existing record without re-collecting all their details: - **Magic link** — a short-lived email link triggers re-identification. - **Passkey** — initiates a WebAuthn registration or assertion ceremony. ## Legal Basis and Required Fields The `processing.legal-basis` value determines which fields within `notice` and `access-event.consent` are expected: | Legal basis | `notice` | `access-event.consent` | |---|---|---| | `uk-consent`, `uk-explicit-consent` | **Required** | **Required** | | All other bases | Must be null | Must be null | For legitimate interests records, `lia-reference` should be supplied on the lead controller entry within `record-metadata.controller-arrangement`. For public task or legal obligation records, `statutory-reference` should be supplied on the lead controller entry. ## Access Record Lifecycle Records are never hard-deleted. All state transitions are recorded with timestamps. ``` [ACTIVE] ──revoke──▶ [REVOKED] [ACTIVE] ──expiry──▶ [EXPIRED] [DISCOVERED] ──claimed──▶ [ACTIVE] [DISCOVERED] ──expiry──▶ [EXPIRED] ``` `REVOKED` represents consent withdrawal (consent records) or the Controller removing their registration (non-consent records). Data Providers must deny access for any record not in `ACTIVE` state with a future (or null) expiry. `DISCOVERED` is a sparse, read-only state created by the DCC when it detects historic meter data requests from an organisation that has not yet registered as a Data User. These records are visible to Customers for transparency but cannot be used to authorise data release. When the organisation onboards as a Data User and registers a full access record for the same MPxN, the DISCOVERED record is superseded and transitions to `ACTIVE`. ## Authentication All endpoints except `GET /access-records/{ak}` require a bearer token from `GET /auth/token`. Tokens expire after 7200 seconds. ## Versioning URI-based versioning. Current version: `v1`. version: 0.0.16 contact: name: Auth Energy email: contact@auth.energy url: https://docs.auth.energy/consent license: name: Proprietary servers: - url: https://api.central.consent/v1 description: Production security: [] tags: - name: Identity Records description: > Endpoints for Data Users to create and manage Identity Records, which hold the person-property relationship (MPxN, address, move-in date, identity verification evidence) separately from access records. Supports re-identification of returning customers via email magic link or WebAuthn passkey. - name: Re-identification description: >- Endpoints for initiating and confirming customer re-identification flows. Supports magic link, passkey assertion, and passkey registration — both for the same Data User (same-DUID) and for a second Data User linking to an existing Identity Record created by another Data User (cross-DUID). In the cross-DUID flow the `ir` key is never exposed to the initiating Data User — the register resolves it internally after the customer completes the challenge. - name: Authentication description: Obtain bearer tokens for authenticated endpoints. - name: Data Users description: > Endpoints for Data Users (Processors) to register and manage access records on behalf of their Controller customers. - name: Data Providers description: > Endpoints for Data Providers (EDPs) to verify access records and look up registered Data User organisations before releasing meter data. Includes access record verification via access key and Data User directory lookup by DUID, allowing EDPs to confirm both that a specific record is active and that the organisation behind it is in good standing. - name: DCC description: > Endpoints restricted to Smart DCC system credentials. Covers two responsibilities: (1) submitting discovered access records derived from historic meter transaction logs — sparse, read-only records that surface to customers for transparency but cannot authorise data release, superseded when the organisation registers as a Data User; and (2) submitting Change of Tenancy events, which trigger `tenancy.change` webhooks to all Data Users with active access records on the affected MPxN. - name: Customer Portal description: > The centralised Customer Consent Portal is a standalone web service at https://portal.central.consent. It has no API endpoints — Data Users link customers to the portal via a plain URL carrying `ir` or `mpxn` and an optional `return` parameter. The portal authenticates the customer directly using the re-identification mechanisms on their Identity Record (passkey, magic link, or supplier OAuth fallback). This tag documents the portal behaviour and the `consent.withdrawal` webhook it fires on revocation. - name: Webhooks description: > Endpoints for Controllers to register and manage webhook subscriptions. The register dispatches event payloads to registered callback URLs when consent records are approaching expiry or when a Change of Tenancy is recorded against an MPxN with active access records. paths: /cot-events: post: tags: - DCC summary: Submit a Change of Tenancy Event description: | Records a Change of Tenancy (CoT) against an MPxN and triggers `tenancy.change` webhooks to all Data Users with one or more `ACTIVE` access records on that MPxN. **Authentication:** Restricted to DCC system credentials. Standard Data User bearer tokens are rejected on this endpoint with `403`. **What the register does on receipt:** 1. Records the CoT event for audit with the MPxN, effective date, and DCC source reference. 2. Identifies all `ACTIVE` access records for the MPxN across all registered Data Users. 3. Fires a `tenancy.change` webhook to each affected Data User, including the `affected-aks` array so Data Users can perform targeted revocations without a separate list query. 4. Returns a summary of Data Users notified and records affected. **What the register does NOT do:** Automatically revoke access records. Revocation is the Controller's responsibility on receipt of the webhook. CoT events from the DCC can occasionally be false alerts; Controllers should verify before revoking records with non-occupancy legal bases (e.g. `uk-public-task`, `uk-legitimate-interests`). **Idempotency:** Submitting the same `mpxn` + `effective-date` + `source-reference` returns `200` and does not re-fire webhooks. **PII:** The payload contains only the MPxN and the effective date. No new occupant name, address, or contact details are included. operationId: submitCotEvent requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/CotEventRequest' example: mpxn: '1234567890123' effective-date: '2026-04-01' source-reference: MPAS-COT-2026-03-00142 responses: '200': description: > Duplicate event — same `mpxn`, `effective-date`, and `source-reference` already recorded. No webhooks re-fired. content: application/json: schema: $ref: '#/components/schemas/CotEventResponse' '201': description: > CoT event recorded and `tenancy.change` webhooks dispatched to all affected Data Users. content: application/json: schema: $ref: '#/components/schemas/CotEventResponse' example: response: resource: /v1/cot-events timestamp: '2026-03-20T09:15:00Z' transaction-id: tid_9f8e7d6c5b4a9f8e7d6c5b4a mpxn: '1234567890123' effective-date: '2026-04-01' source-reference: MPAS-COT-2026-03-00142 active-records-affected: 2 data-users-notified: - duid_691df0c788ca043403b7fa90 - duid_aabbcc112233445566778899 '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorised' '403': description: > Caller does not hold DCC system credentials. This endpoint is not accessible to standard Data User bearer tokens. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': $ref: '#/components/responses/InternalServerError' security: - bearerAuth: [] components: schemas: CotEventRequest: type: object description: > A Change of Tenancy notification submitted by the DCC. Triggers `tenancy.change` webhooks to all Data Users with active access records on the affected MPxN. properties: mpxn: $ref: '#/components/schemas/MPxN' effective-date: type: string format: date description: > The date on which the change of occupancy takes effect. Data access registered on behalf of the previous occupant should cease no later than this date. example: '2026-04-01' source-reference: type: string maxLength: 255 description: > The MPAS or DCC internal reference for this CoT notification. Used for idempotency and audit traceability. Submitting the same `mpxn` + `effective-date` + `source-reference` a second time returns `200` without re-firing webhooks. example: MPAS-COT-2026-03-00142 required: - mpxn - effective-date - source-reference CotEventResponse: type: object description: > Returned after a Change of Tenancy event is recorded. Summarises the Data Users notified and the number of records affected. properties: response: $ref: '#/components/schemas/ResponseMetadata' mpxn: $ref: '#/components/schemas/MPxN' effective-date: type: string format: date example: '2026-04-01' source-reference: type: string example: MPAS-COT-2026-03-00142 active-records-affected: type: integer description: > Number of `ACTIVE` access records across all Data Users on this MPxN at the time the event was processed. example: 2 data-users-notified: type: array description: > DUIDs of Data Users that received a `tenancy.change` webhook. Each entry had at least one `ACTIVE` access record on the MPxN. items: $ref: '#/components/schemas/DataUserId' example: - duid_691df0c788ca043403b7fa90 - duid_aabbcc112233445566778899 required: - response - mpxn - effective-date - source-reference - active-records-affected - data-users-notified ErrorResponse: type: object properties: response: $ref: '#/components/schemas/ResponseMetadata' errors: type: array minItems: 1 items: $ref: '#/components/schemas/ErrorDetail' required: - response - errors MPxN: type: string pattern: ^(?:[0-9A-HJ-NPR-Z]{2}[0-9]{8,10}|[0-9]{10})$ description: >- Meter Point Administration Number (MPAN) or Meter Point Reference Number (MPRN). example: '1234567890123' ResponseMetadata: type: object properties: resource: type: string example: /v1/access-records/ak_691df0c788ca043403b7fa90 timestamp: type: string format: date-time example: '2026-03-11T12:00:00Z' transaction-id: type: string description: >- Unique identifier for this request/response pair. Quote in support enquiries. example: tid_691df0c788ca043403b7fa90 required: - resource - timestamp - transaction-id DataUserId: type: string pattern: ^duid_[0-9a-f]{24}$ description: > Unique identifier for a registered Data User organisation, issued by the register at onboarding. example: duid_691df0c788ca043403b7fa90 ErrorDetail: type: object properties: error-code: type: string example: VAL001 message: type: string example: Field 'mpxn' does not match the required pattern. required: - error-code - message responses: BadRequest: description: The request was malformed or failed validation. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' Unauthorised: description: Missing or invalid bearer token. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' InternalServerError: description: An unexpected server-side error occurred. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- JWT from `GET /auth/token`. Pass as `Authorization: Bearer `. Expires after 7200s. ````