Zquence gives your product tenant-scoped APIs for users, KYC, transactions, and signed webhooks. Most teams integrate in this order:
1

Get credentials

Create or open your tenant in the dashboard, then copy your credentials and webhook signing secret.
2

Call the API from your backend

Add the x-api-key and x-api-secret headers to server-to-server requests. Do not call Zquence directly from a browser with your secret key.
3

Create or sync users

Add users to your tenant before starting KYC or transaction flows.
4

Handle webhooks

Add a webhook URL in the dashboard and verify every incoming event with your webhook signing secret.
5

Build the product flow you need

Start with KYC, then add transactions as your product requires.

​
Start here

Quickstart

Make your first API call and receive a signed webhook.

Using the API

Add a small backend helper for authenticated requests.

Webhooks

Receive events, verify signatures, and handle retries.

API reference

Look up endpoint paths, parameters, and response shapes.

​
Common integration paths

Verify a user

Create a verification session and wait for the final KYC webhook.

Sync users

Create one user or import users in bulk.

Run transactions

Create a transaction, invite counterparties, and track lifecycle events.

​
Developer rules of thumb

  • Keep secret keys only on your backend.
  • Store tenantId, Zquence IDs, and webhook event IDs in your database.
  • Send Idempotency-Key on create requests your system may retry.
  • Treat webhooks as the source of truth for async outcomes.
  • Log x-request-id from failed API calls so support can trace them.
If you are unsure where to begin, complete the Quickstart, then build the one product guide that matches your workflow.