API reference
API overview
The Zpad app runs on this API. Anyone can read coin data with it.
Address
The API lives on the app's own address. Every path in these docs is relative, for example /api/v1/coins. To call it, put the address you open Zpad on in front of the path.
The examples show the full address once this page has loaded in your browser.
Format
- Requests and answers are JSON, except the launch form, which is sent as multipart form data.
- Answers under
/api/v1come in one envelope:success,messageanddata. - Three parts answer plain JSON without the envelope: the launch routes (
/api/v1/launch/...), sign in (/api/auth) and the Solana relay (/api/rpc). Their pages say so.
{
"success": true,
"message": "<what happened, in plain words>",
"data": <the answer>
}How to read the shapes
number,stringandbooleanstand for a value of that type.- Values in angle brackets, like
"<coin address>", are examples of what goes there. a | bmeans either one.- Every other value is exactly what the API sends.
Units
Caching
Sections
Good to know
- The API serves the Zpad pages first. Shapes follow what the pages need.
- Routes under
/api/cronare internal jobs. They need the server's own secret and are not part of the API. - Changes are listed in the Changelog.