Skip to content
ZytePedevelopersDashboard
DocsDeveloper tools
Developer tools

Code examples and tools

Download inspectable signing examples and the public OpenAPI specification.

Choose your language

Select Node.js, Python, PHP, Ruby, Java or cURL on a workflow or API reference page. Required, Optional and Conditional labels explain what to include. Labels are not included when you copy code.

For Node.js, save signing.mjs for merchant HMAC or plugin-signing.mjs for plugin requests beside your example. For Python, save zytepe_signing.py in the same directory. The helpers use standard cryptography libraries and server-side environment variables. These are source examples, not an SDK package.

Node.js and Python request examples are tested with mocked transports, without contacting the production API. PHP 8+ (with cURL) Ruby and Java 17+ examples include signing inline; validate them in your server environment before use. Replace example data, configure your approved server and review product enablement before sending a request.

OpenAPI specification

Download the OpenAPI 3.1 specification. It contains only the 14 public integration candidates, with per-operation authentication and source request/response examples. Incomplete schema rules are not filled in from assumptions.

Postman setup

You may import the specification into Postman for reference. This is not a preconfigured signing collection. Before sending requests, implement the authentication scheme, resolve all variables in the URL, and sign the exact outgoing body and query representation. Keep credentials in private local variables.

GET has no body. Payout retries keep the same idempotency key; every HMAC HTTP request needs a fresh nonce. There is no live request tool on this site.

cURL request shape

Reference pages show the HTTP request shape with signature placeholders where appropriate. Those placeholders must be generated for the exact request by your backend; they are not reusable working credentials.