Skip to main content
Create an invoice with POST /public/v1/invoices/create on the sandbox or production API host. Send JSON with Content-Type: application/json and your server-side API key in the x-api-key header. The production OpenAPI schema is the source of truth for the deployed field types and required fields.

Request body

Only currency and amount are required by the current OpenAPI schema. idempotencyKey, order_no, and callbackUrl are strongly recommended for a reliable store integration. Unknown fields are not part of the published OpenAPI schema. For example, callbackUrl uses camel case while order_no and the redirect URL fields use underscores. Follow the schema exactly rather than converting every key to one naming convention.

Response fields to persist and compare

The response includes id, invoice_url, status, order_no, amount, settlement_currency, currency, and expires_at, as well as fees, payment totals, and optional redirect URLs. Store the invoice ID and your payment attempt before opening invoice_url. For example, an invoice requested in USDT can have settlement_currency: "USDT" and currency: "USDT_TRON". Match your order to settlement_currency and the requested amount, then require completed from the authenticated API before fulfillment. See callbacks and security. See Statuses and lifecycle for every invoice status and how to handle it. The create-invoice example shows TypeScript, Python, PHP, and cURL. The live OpenAPI documents for sandbox and production show the schemas currently deployed in each environment.