Endpoint
Authentication
This endpoint requires authentication via API key. Include your API key in the X-API-Key header:
Path Parameters
Request Body
Request Example
Response
Success Response
Status Code: 200 OK
Response Fields
Error Responses
401 Unauthorized
Returned when authentication fails. See the authentication errors section for details.
404 Not Found
Returned when no active clickwrap exists for the given slug.
500 Internal Server Error
Returned when the request fails due to a server error.
Notes
accepted: true means the user has accepted the currently active version specifically. If the clickwrap was updated since the user last accepted, accepted will be false even though the user accepted a previous version.
Use the version_number in the response to detect when a user accepted an older version and needs to re-accept the latest terms.
Use Cases
This endpoint is useful for:
- Access gating - Block a user from proceeding until they have accepted the current terms
- Re-consent checks - Determine on login or feature access whether the user’s acceptance is still current
- Audit queries - Programmatically verify acceptance status before performing a regulated action