Endpoint
Authentication
This endpoint requires an OAuth access token. Send it as a bearer token:clickwrap:read
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
Every field is optional. An empty body ({}) returns the newest 50 events for the clickwrap.
Request Example
Response
Success Response
Status Code:200 OK
Response Fields
Event Object 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 clickwrap exists for the given slug.422 Unprocessable Entity
Returned when the request body fails validation: for example, only one ofmetadata_key and
metadata_value is sent, from_date is later than to_date, page_size is outside 1-200, or an
event_types entry is not a known event type.
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
The search covers every version of the clickwrap, including archived ones, so it returns a user’s
full history. Unlike the other clickwrap endpoints, it also works for a clickwrap that has no
published version yet.
For personalized agreements,
metadata.template_variables contains the values supplied through
the v2 capture request. The acceptance PDF uses
those values with the recorded version’s template. PDF generation is asynchronous, so
certificate_attachment_id may be absent when you first retrieve the event.The result is organization-global. Every token issued for the same organization gets the same
answer - the token’s user is used only to authenticate and scope-check the request.
Use Cases
This endpoint is useful for:- Compliance evidence - Pull every acceptance a user has recorded, with the version, IP address, user agent, and metadata of each
- Reconciliation - Find events by your own metadata (e.g. an order or session ID) to match them to records in your system
- Funnel reporting - Count
viewedversusacceptedevents over a date range