A valid request URL is required to generate request examples{
"acceptances": [
{
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"contact_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"contact": {
"email": "<string>",
"name": "<string>"
},
"version_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"version": 123,
"accepted_at": "2023-11-07T05:31:56Z",
"ip": "<string>",
"user_agent": "<string>",
"source": "signup"
}
],
"total": 123
}{
"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"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}Who agreed, and to which words
Requires legal:manage. The evidence: one row per person per version, newest first, with the address the click came from and the browser it was made in.
source says which door it arrived through and is the server’s own answer rather than a field anybody sends: signup (collected in the same request that created the account — the strongest of the three, since there was no account before the agreement), session (a person ticked the box while signed in, from the portal or your own app), api (your backend recorded an agreement that happened in your sign-up form, which is how a federated environment does this).
contact is null when the person has been erased. That is the record doing what it exists to do: an acceptance survives an erasure, holding ids and a version number, while the address and the user agent are scrubbed off it — see the privacy documentation on what an erasure keeps and why.
A valid request URL is required to generate request examples{
"acceptances": [
{
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"contact_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"contact": {
"email": "<string>",
"name": "<string>"
},
"version_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"version": 123,
"accepted_at": "2023-11-07T05:31:56Z",
"ip": "<string>",
"user_agent": "<string>",
"source": "signup"
}
],
"total": 123
}{
"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"
}
}{
"error": {
"code": "forbidden",
"message": "your role does not allow this action"
}
}Authorizations
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.
Headers
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.
Path Parameters
Query Parameters
Page size. Values outside 1–200 fall back to 50.
1 <= x <= 200x >= 0