API reference
Errors
What a failed request looks like.
Shapes
Routes under /api/v1 answer errors in the envelope, with success: false. The message is plain words you can show to a person.
The launch routes, sign in, and the rate limit and CSRF answers of a few routes are plain { error } objects. Some carry a short code: unauthorized, csrf or rate. Each endpoint's Errors table says which.
{
"success": false,
"message": "No such coin here.",
"error": "No such coin here.",
"data": null
}{
"error": "Connect your wallet and sign in first.",
"code": "unauthorized"
}{
"jsonrpc": "2.0",
"id": <your id>,
"error": { "code": -32601, "message": "Method not allowed here." }
}Status codes
Rules
- Errors are never cached.
- A list that cannot be read answers an empty list, never made up numbers.
- One coin that cannot be read answers 500, never 404. A 404 always means the coin is not here.
- When a launch route fails after you paid, the message says so: your launch is safe and keeps going on its own.