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 11, 2026

Register or Update an Access RecordRegister a new access record on behalf of a Controller, or update an existing one by supplying the `ak` query parameter. 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 `processing.lia-reference`; set `notice` and `access-event.consent` to null. - **Public task / legal obligation** — populate `processing.statutory-reference`; 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`.

Obtain Bearer Token

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

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