Endpoint
Authentication
This endpoint requires an OAuth access token. Send it as a bearer token:clickwrap:write
Clickwrap is the one
/v2 surface with no acting user. The subject of a clickwrap event is
user_identifier, an opaque string you supply for your own end user, which is never resolved
against Chamelio’s users. These endpoints are authorized by organization and scope alone, so
client_credentials tokens work here without restriction.Path Parameters
Request Body
Request Example
Response
Success Response
Status Code:200 OK
Response Fields
Error Responses
401 Unauthorized
Returned when the access token is missing, unknown, revoked, or expired, or when anX-API-Key was
sent instead of a bearer token. See OAuth error responses.
403 Forbidden
Returned when the token does not carry the required scope.404 Not Found
Returned when no active clickwrap or active version exists for the given slug.422 Unprocessable Entity
Returned when an acceptance is recorded before its prerequisite events. Anaccepted event requires
a prior viewed event, and a scroll_and_accept clickwrap additionally requires a prior
scrolled_to_bottom event.
429 Too Many Requests
Returned when your organization exceeds its per-minute request limit.500 Internal Server Error
Returned when the request fails due to a server error.Notes
Because this is a server-to-server endpoint, the API caller’s IP address and user agent are never used as the end user’s origin data. Always pass the actual end user’s
ip_address and user_agent in the request body for legally valid acceptance records.Use Cases
This endpoint is useful for:- Server-side consent capture - Record acceptance from a backend flow where the clickwrap was rendered in your own UI
- Audit trails - Store
ip_address,user_agent, andmetadata(e.g. session ID, product context) for compliance records - Multi-step flows - Record intermediate events (
viewed,scrolled_to_bottom) before the finalacceptedevent