Skip to main content
TermDefinition
App IDA public identifier for your integration. Used in the client SDK to initialize ClickTerm. Safe to include in frontend code.
App KeyA secret credential for your integration. Used only for server-to-server API calls (e.g., Signature verification). Must never be exposed in client-side code.
Certificate of AcceptanceA digitally signed PDF that proves a specific end user accepted a specific clickwrap version at a specific time. Includes metadata such as user ID, timestamp, IP address, and browser information.
ClickwrapA digital agreement that requires an explicit user action (e.g., clicking “I Agree”) to confirm acceptance. Creates an auditable record of consent.
Clickwrap AgreementThe complete PDF document combining the accepted clickwrap content (with resolved placeholders) and the Certificate of Acceptance. The recommended document for legal record-keeping.
Clickwrap EventA record of an end user’s interaction with a clickwrap — including the action taken (accepted, declined, pending), the template version shown, and technical metadata.
Effective versionThe template version currently being served to end users. A version becomes effective when its effectiveAt timestamp is reached.
End UserA person who interacts with a clickwrap agreement in your application. Identified by the endUserId you provide.
End User IDA string identifier (max 256 characters) you assign to each end user. Used to track consent across events and templates.
IntegrationA connected application (web or mobile) in your ClickTerm workspace. Each integration has its own App ID and App Key.
Major versionA template version that requires all users to re-accept. Published when legal terms change meaningfully. Labeled as whole numbers (1.0, 2.0, 3.0).
Minor versionA template version for non-critical changes (typos, formatting). Users who accepted the latest major version are not re-prompted. Labeled as decimals (1.1, 1.2).
PlaceholderA dynamic field in a template (e.g., [[fullName]], [[email]]) that gets replaced with real values at runtime when the clickwrap is presented.
Scheduled versionA published template version whose effectiveAt date is in the future. Not yet served to end users.
SignatureA signed token returned by the ClickTerm SDK after an end user accepts or declines a clickwrap. Must be verified on your backend via POST /clickwrap/verify.
Superseded versionA template version that has been replaced by a newer effective version. Retained for auditing but no longer served to end users.
TemplateA reusable legal document (e.g., Terms of Service, Privacy Policy) managed in the ClickTerm dashboard. Contains the text, formatting, placeholders, and version history.
WorkspaceYour organization’s ClickTerm account. Contains templates, integrations, team members, and billing settings.