API Reference
The Zet API is organized around REST principles. All endpoints accept JSON request bodies and return JSON responses.Base URL
Authentication
All endpoints require an API key via thex-api-key header. See Authentication for details.
Endpoint groups
Wallets
Create and manage Smart Wallets for your users.
On-Ramp
Buy crypto with Nigerian Naira (NGN).
Off-Ramp
Sell crypto for NGN to a bank account.
Swap
Swap tokens on the same chain or across chains.
Cross-Chain Transfer
Bridge tokens across different blockchains.
Webhooks
Register endpoints for real-time event notifications.
Transactions
Query transaction history and details.
Common patterns
Quotes → Execute
Most operations follow a two-step pattern:- Get a quote — call the quote endpoint to get pricing, fees, and a
quoteId - Execute — pass the
quoteIdto initiate/execute the transaction
Custodial vs Non-Custodial
Every execute/initiate endpoint accepts either:walletId— for Zet-managed wallets (custodial, gasless)sourceAddress/destinationAddress— for user-managed wallets (non-custodial)
Idempotency
Pass areference string with your initiate/execute calls. If you retry with the same reference, the existing transaction is returned instead of creating a duplicate.
Pagination
List endpoints supportpage and limit query parameters. Response includes a meta object with pagination info.