Limits
| Endpoint type | Rate limit | Billing |
|---|---|---|
POST /clickwrap/verify | 1,000 requests per hour (per app + IP). Also subject to your plan’s event quota. | Counted toward billing |
GET endpoints (clickwrap, customizations) | 1,000 requests per hour (per app + IP) | Free |
GET endpoints (events, certificates) | No explicit rate limit | Free |
SDK requests (ClicktermDialog.show()) | No explicit rate limit | Free |
Only
POST /clickwrap/verify calls count toward your billing. All other requests
are free. See clickterm.com/pricing for pricing details.Rate limit responses
If you exceed the rate limit, the API returns:Best practices
- Cache consent status — Call
GET /clickwraps/{endUserId}/statusonce per session rather than before every action - Rate limit your own verification calls — Add a Captcha or rate limiter before
POST /clickwrap/verifyto prevent abuse from end users - Don’t poll for events — Use the verification response directly rather than polling event details
- Batch certificate downloads — If archiving certificates, spread downloads over time rather than fetching all at once
- Implement retry logic — Use exponential backoff for 429 responses