Skip to main content
POST
Record that the account owner accepted one of the account terms

Authorizations

Authorization
string
header
required

Enter Auth0 JWT token

Headers

Zuba-Account-Id
string<uuid>

Optional. Names an owned sub-account (UUID); when present, the application must belong to it. Omit to act on any application in your workspace. Naming an account this key does not own returns 403 not_account_owner.

Path Parameters

applicationId
string<uuid>
required
slug
string
required

The document’s slug as the requirements response names it.

Example:

"terms-of-service"

Body

application/json
documentVersion
string
required
Example:

"2026.08.07"

attestation
object

Required when acknowledging with an API key on an owner's behalf. Omitted by a dashboard session, whose acknowledgment is the signed-in user's own.

Response

acknowledgedAt
string
required
Example:

"2026-08-07T10:22:33.123Z"

acknowledgedByActorType
enum<string> | null
required

Which surface recorded this acknowledgment. An api_key row always carries a complete attestation; a dashboard_user row never does, because the signed-in click is itself the evidence. null names a row that asserts neither, so a missing attestation is never ambiguous.

Available options:
dashboard_user,
api_key
id
string
required

UUID of the ack row.

slug
string
required
version
string
required
attestation
object | null

The acceptance evidence recorded with this acknowledgment, or null when the owner acknowledged in the Zuba dashboard themselves.