Zquence V2 exposes 15 tenant-facing external API groups for enterprise integrations. These groups are intended for tenant systems such as CRMs, BI dashboards, SharePoint workflows, compliance queues, and internal portals. For the detailed endpoint list, use the API reference sidebar groups. Start with KYC API, Document review API, and Webhook events.
Status means API-key readiness for tenant external integrations, not whether internal admin console routes exist. A backend route must have an API-key scope before tenants should build against it with API keys.

​
Current scope model

API key creation supports these scopes today:

​
API-key access rule

Every API-key route is opt-in. Implemented routes require one of the scopes above. Default dashboard routes reject API-key headers and require a user session. Every live and sandbox API key receives the complete scope list when it is created. Existing active keys are synchronized additively when documented scopes are introduced. There is no public API endpoint to update scopes on an existing key. Keep these APIs internal to the Zquence admin console or super-admin operations:
  • Provider credentials and lifecycle mutation.
  • Provider cost and pricing catalog mutation.
  • Tenant deletion and recovery mutation.
  • Cross-tenant reconciliation recovery actions.
  • Platform legal content assignment and platform billing setup.

​
Integration checklist

  1. Create separate sandbox and live keys.
  2. Confirm the key lists the complete current scope catalog.
  3. Include x-api-key and x-api-secret; use environment headers only where endpoint docs require them.
  4. Use pagination for list endpoints.
  5. Treat 429 responses as rate-limit signals and back off.
  6. Verify webhook signatures and deduplicate on event.id.
  7. Poll sync events if your tenant runs API-only or needs a recovery path for missed webhook delivery.
  8. Store PII, exports, and webhook payloads according to tenant data-residency policy.