Integrations
Connect PDF workflows without expanding data exposure.
ClearPDF reads integration readiness from the backend provider registry. Local contracts and fail-closed adapter seams are shown separately from public launch claims, which remain blocked until retained provider approval, credential, and live-transfer evidence exists.
Integration readiness unavailable
Authentication required
Backend status
Provider coverage
No integration providers returned
The integrations API responded without provider readiness records for the current principal.
Connection monitor
Status and recovery states
The backend registry keeps local adapter readiness separate from credential, approval, and live-transfer gates.
API contracts
Boundaries first
Connect URLs return provider authorization URLs, requested scopes, short-lived state, and callback fields. Backend responses never return provider tokens.
GET /v1/integrations
POST /v1/integrations/{provider}/connect-url
POST /v1/integrations/{provider}/callback
POST /v1/integrations/{provider}/import-jobs
POST /v1/integrations/{provider}/export-jobs
POST /v1/integrations/{provider}/webhook-events
GET /v1/integrations/{provider}/sync-statusLaunch gates
Required retained evidence
GateStatusRetained evidence required
Data categoryUsed forRetention posture
Provider file IDsImport/export correlationBackend contracts require hashed provider identifiers in returned audit metadata.
Audit-safe metadataAdmin review and transfer historyNo metadata declared
OAuth codes and tokensConnection setupAccepted only at the callback boundary; token storage is declared as encrypted at rest and tokens are not present in API responses.