Skip to main content
Version: 1.0

Click Render API

The Propper Click Render API serves consent and clickwrap experiences as JSON payloads optimized for edge caching. Client-side SDKs fetch rendered templates from this API to display consent flows to end users.

Base URL​

https://api.propper.ai/v1/click/render

Authentication​

OAuth 2.0 Bearer token:

Authorization: Bearer <access_token>

OAuth Scopes​

  • click:admin — Full administrative access
  • click:read — Read-only access to rendered experiences

Key Endpoints​

  • Render — Fetch rendered consent experiences by deployment key

Request correlation​

Every response (success and error) includes an x-request-id header (a UUID) and a traceparent header (W3C Trace Context). Error bodies also carry the same id as requestId. Quote x-request-id when contacting support to pinpoint the exact request, and use it to correlate the API with your own logs. Send your own traceparent to tie a multi-call workflow under one trace.

Authentication​

OAuth 2.0 Bearer token

Security Scheme Type:

http

HTTP Authorization Scheme:

bearer

Bearer format:

JWT

Contact

Propper Support: support@propper.ai

URL: https://propper.ai