Skip to main content
POST
/
v1
/
consent
Register consumer consent
curl --request POST \
  --url https://example-supplier.co.uk/v1/consent \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{}'
{
  "data": {
    "registration_id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
    "tariffs": [
      {
        "mpxn": "1012345678901",
        "tariff_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
      }
    ]
  }
}

Authorizations

​
Authorization
string
header
required

OAuth 2.0 Authorisation Code flow for RTI User authentication and consumer consent. Each supplier operates its own OAuth server. In production, substitute the placeholder host with the relevant url from the Supplier Register. OpenAPI does not permit URI templates in security scheme URLs, so a placeholder is used here.

Body

application/json

No body required. Consumer identity is resolved from the OAuth token.

Empty body — consumer identity is derived from the bearer token.

Response

Consent registered. Returns the registration ID and in-scope metering points.

​
data
object
required
Last modified on March 28, 2026