API Reference

The Seqlense Monitoring API gives programmatic access to the Seqlense compliance monitoring platform: identities (KYC/KYB), wallets, order-book data, market-abuse scans, alerts and their notification channels.

Authentication. Send an API key as a bearer token: Authorization: Bearer sq_.... Create keys from Settings → Developer on monitoring.seqlense.com. Every request is scoped to the organization that owns the key, and to the workspace (production or development) the key was created for.

Conventions. Bodies are JSON. Copy paths exactly, trailing slash included. A POST or PUT must carry a JSON body even when no field is needed: send {}, an empty body answers 404. Bodies are capped at 2 MB. Errors are always {"error": "..."}.

Status codes. 400 means the request itself is wrong and resending it unchanged will fail again. 401: no valid key. 403: authenticated but not allowed. 404: not found in your workspace. 500: the server failed to complete the call (a write that did not land); it is safe to retry. 503: a dependency is temporarily unavailable; retry after a short wait (Retry-After when present).

Permissions. A few operations (merge, bulk deletes, the trash, the order-book purge) are restricted to workspace admins. An API key carries the role of the member who created it, checked on every call: a key created by an admin can call them while that member is still an admin, a member's key cannot. API keys are managed from a signed-in session only: a key cannot create or revoke keys.

Endpoints by category