API Reference
Every KiiChain Pay backend endpoint, plus the official Postman collection.
This section documents every endpoint of the KiiChain Pay backend API. Endpoints are grouped by module.
Both this reference and the Postman collection are regenerated automatically on every KiiChain Pay backend release.
Generating API keys covers authentication and request signing. The Guides walk through full on-ramp, off-ramp, FX and DEX flows end to end.
Try it in Postman
You can explore the API in the KiiChain Pay Backend Postman collection. It has every endpoint in this reference, ready to run, with signing already wired up.
What you get:
Requests grouped by RPC server. Folders follow the service boundaries — one per
<Module>QueryServer(reads) and<Module>MsgServer(writes). Example:UsersQueryServer,TicketsMsgServer— so each folder maps into a module in this reference.Signing handled for you. A pre-request script computes the Ed25519 signature for every write request (
POST/PATCH/PUT/DELETE) from your environment'sapi_keyandpriv_key, following the scheme described in Sign write requests. No manualx-timestamp/x-signatureheaders needed.A ready-made environment. Fork it alongside the collection and fill in:
base_url
https://backend.pay.kiichain.io (production), or the staging base URL.
api_key
Your api_key from Generating API keys.
priv_key
Your priv_key — the pre-request script uses this to sign write requests.
Getting started
Fork the collection and its environment into your own Postman workspace (top-right Fork button on each).
Open the forked environment, select it as active, and fill in
api_key, andpriv_key.Send a read request first (You can try
MeatUsersQueryServer) to confirm your API key is valid.Send a write request (Anything with
*MsgServer). The pre-request script signs it automatically.
Treat priv_key like any other private key. Postman environment values are visible to anyone you share the workspace with — don't fork a copy with a production key into a shared team workspace.
Last updated