The Zquence API is plain JSON over HTTPS. You can use any HTTP client. The important part is to keep authentication and error handling in one backend helper.

Required headers

Every server-to-server request needs:
Use test keys with the sandbox environment and live keys with production.

Create resources safely

For create/update actions that your system might retry, send an Idempotency-Key.
Node.js
Use a stable key from your own system, such as an order ID, user ID, or job ID.

Handle errors by code

Errors use a stable shape:
In your app:
  • Show validation errors next to the relevant field.
  • Retry 429 and 5xx errors with backoff.
  • Log requestId for support.
  • Do not retry validation or permission errors without changing the request.

Production checklist

  • Store keys in a secrets manager.
  • Use separate keys for test and live.
  • Add timeouts to all HTTP calls.
  • Add Idempotency-Key to retried POST requests.
  • Verify all webhooks before processing them.
  • Store webhook event IDs so duplicate deliveries do not double-process work.

Where to go next

Authentication

Key types, rotation, and where secrets belong.

Errors

Error codes and retry behavior.

Idempotency

Make retries safe.

API reference

Endpoint-by-endpoint details.