SDKs

Everything the SDKs do is plain HTTPS against the API: any language can call it. The SDKs save you the plumbing: types for every operation and object, retries that are always safe, paging, typed errors and webhook verification. Their types are generated from the same OpenAPI document as the reference, so they always match it.

Which one#

• On your server: Node or Python. They hold the API key: never use them in a browser.
• In the browser: the browser SDK joins a live session with the token your server started; the React components wrap it, and embed a portal for your signed-in users.
• For an AI assistant on your own machine: the MCP server gives it the API as tools.

What they all do#

• Every operation is a method, named after its operation id: createPersona in Node, create_persona in Python. The reference shows each operation's name and a call in both.
• Safe retries: a 429 is retried after the pause it asks for; no answer, 502, 503 and 504 are retried with a growing pause (twice by default) only where a retry can't do anything twice: reads, updates, deletes, and the creating calls that take an Idempotency-Key, which the SDK sends for you, the same on each retry.
• The newest contract: every request sends Zentiq-Version: 2026-10-01, whatever the key's own.
• Pages: paginate walks a list for you.
• Typed errors: one error class per kind of failure, all with code, status, message, param, details and the requestId.
• Webhooks: verifyWebhook checks the signature and the timestamp, and gives you the event, typed by its type.

The SDKs' versions follow the contract: 1.x speaks 2026-10-01. A later contract that changes something incompatibly comes with a new major version.