A valid request URL is required to generate request examples{
"acceptances": [
{
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"document_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"slug": "<string>",
"title": "<string>",
"enforcement": "required",
"version_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"version": 123,
"summary": "<string>",
"accepted_at": "2023-11-07T05:31:56Z",
"ip": "<string>",
"user_agent": "<string>",
"source": "signup"
}
]
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}What one contact agreed to
Requires legal:manage. Everything this person consented to, newest first: which document, which version, when, and through which door.
It is the evidence with the PERSON on screen — the other axis of GET /v1/organization/legal/{id}/acceptances, which asks who agreed to one document. This is the question a support conversation starts from, because the person is who the conversation is about.
The permission is legal:manage and not the contact’s own read, deliberately: customers:read reaches every seat, while what somebody consented to is not the support floor’s to browse. The document-side answer is gated identically.
summary is the sentence that was beside the checkbox for THAT version, not the one in force today. A record reports what was on the screen; reading today’s words back would answer a different question in the same shape.
Unpaginated: a document collects an acceptance per customer, but a person accumulates one per document they were asked about, which is a handful.
A valid request URL is required to generate request examples{
"acceptances": [
{
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"document_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"slug": "<string>",
"title": "<string>",
"enforcement": "required",
"version_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"version": 123,
"summary": "<string>",
"accepted_at": "2023-11-07T05:31:56Z",
"ip": "<string>",
"user_agent": "<string>",
"source": "signup"
}
]
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}Autorizações
A staff session token, uk_st_…. Minted by sign-up, sign-in or the two-factor exchange. Only a 401 means it is spent; not_a_member (403) is about the organization named in X-Organization-Id and leaves the token good for the others.
Cabeçalhos
The organization the caller is acting on — the org_… code that appears in the panel URL. It identifies; the membership JOIN is what authorizes, so a forged code reads nothing: the answer is not_a_member (403), which does not mean the session is over. Absent, the session's default organization answers, or — if that membership was revoked while the session was open — any other one the caller still holds.
Parâmetros de caminho
Parâmetros de consulta
Which environment to act in. A view parameter, valid only on the staff surface — a machine credential never chooses its environment, it is resolved from the key.
live, test Resposta
This person's acceptances, newest first.
Show child attributes
Show child attributes