Skip to main content

Endpoint

Authentication

This endpoint requires an OAuth access token. Send it as a bearer token:
Required scope: 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 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 an X-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 exists for the given slug.

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

This endpoint only returns the active (published) version. Draft versions are never exposed on externally authenticated endpoints.
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 the clickwrap_version_id returned here when calling Check Clickwrap Status or Capture Clickwrap Event to correlate acceptances with specific versions.

Use Cases

This endpoint is useful for:
  • Headless consent flows - Fetch clickwrap content server-side and render it in your own UI before capturing acceptance
  • Version awareness - Read the current version_number to decide whether a returning user needs to re-accept
  • Content display - Render content_html in embedded forms or modal dialogs