Skip to main content
POST
Create consent banner

Authorizations

Authorization
string
header
required

API token obtained from the login endpoint or the dashboard

Query Parameters

account_id
string

Which account to act on, as the account's API id. Only meaningful for a user API key, which may reach several accounts — an account key already identifies exactly one and ignores this.

Accepted by the endpoints that declare it; others act on the account the key resolves to on its own.

Optional for reads, where it narrows the request to that account. Required for writes that declare it when the key can reach more than one account: without it the request would act on an account it picked rather than one you named, so it is refused with a 400.

Body

application/json

Consent banner to create

Translations are not accepted here — add them by updating the banner, which is where the account's language entitlement is enforced.

The create payload: every banner setting except enabled, which is not part of it because a new banner is always created disabled — enable it with an update once its content and targeting are set. Sending enabled anyway is not an error, the value is simply ignored.

Response

Created consent banner

data
object

Every setting the update endpoint accepts, plus the read-only fields below — the response is derived from the same list the API permits, so a banner can be read, edited and sent back unchanged.

Example: