Obtain Bearer Token - Auth Energy

GET

/

auth

/

token

Obtain Bearer Token

curl --request GET \
  --url https://api.central.consent/v1/auth/token \
  --header 'Authorization: Basic <encoded-value>'

{
  "bearer-token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "expires": 7200
}

Authorizations

Authorization

string

header

required

Base64-encode account_id:secret_key. Used only on GET /auth/token.

Response

Token issued successfully.

bearer-token

string

required

Example:

"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."

expires

integer

required

Token lifetime in seconds from issue.

Example:

7200

Last modified on March 25, 2026

Create an Access RecordRegisters a new access record on behalf of a Controller. Returns `201` and an `access-token` containing the new access key (`ak`), plus a `Location` header pointing to the created resource. All records use the same `AccessRecord` schema. The `processing.legal-basis` value determines which additional fields are expected: - **Consent bases** — populate `notice` and `access-event.consent`. - **Legitimate interests** — populate `lia-reference` on the lead controller entry; set `notice` and `access-event.consent` to null. - **Public task / legal obligation** — populate `statutory-reference` on the lead controller entry; set `notice` and `access-event.consent` to null. - **Contract** — set `notice` and `access-event.consent` to null. Historic records may be submitted — `access-event.registered-at` may predate `record-metadata.created-at`. If the DCC has previously submitted a `DISCOVERED` record for the same MPxN and organisation, the register will link the two records on creation. The DISCOVERED record is retained for audit; the new full record becomes `ACTIVE`. To update an existing record use `PUT /access-records/{ak}`. **Cross-DUID re-identification:** To create an Access Record linked to an Identity Record originally created by another Data User, include a `reidentification-token` field in the request body (alongside the standard `AccessRecord` fields, without `record-metadata.identity-record-ref`). Obtain the token via `POST /identity-records/reidentify`. The register validates the token and resolves the `ir` internally.

Obtain Bearer Token

curl --request GET \
  --url https://api.central.consent/v1/auth/token \
  --header 'Authorization: Basic <encoded-value>'

{
  "bearer-token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "expires": 7200
}