Skip to main content
There is no official ZLL SDK yet. Official SDKs are coming soon and will handle request signing for you. Until then, you construct and sign every write request by hand. Signing is the work an SDK would otherwise do. The signed payload envelope gives the JSON shape and the exact byte layout you sign over, and common signing mistakes lists the errors that bite first — wrong base64 alphabet, a stale request_id, signing the base64 text instead of the decoded bytes.

​
Code samples in the Trading API reference

The Trading API reference auto-generates curl, Python, and JavaScript samples per endpoint. Those samples build the HTTP request, but they do not sign it. For a signed-body endpoint the generated sample shows payload, signature, and public_key as placeholder base64 strings. It never packs the binary payload, never generates a fresh UUIDv7, and never runs the per-curve signature. Copy it as-is and the exchange rejects it. Treat those samples as request-shape documentation, not runnable code.
Endpoint kindAuthGenerated sample
ReadsX-API-KEY or X-DEVICE-KEY headerRunnable — paste your key and send
Signed writesClient-side signature over a binary payloadDocumentation-only — the opaque base64 fields are placeholders
Use the generated samples directly only for header-authenticated reads. For writes, take the decoded-body shape from the reference and sign it from your own client using the signed payload procedure.