Docs menuErrors

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.

/api/v1 routes
{
  "success": false,
  "message": "No such coin here.",
  "error": "No such coin here.",
  "data": null
}
Plain answers
{
  "error": "Connect your wallet and sign in first.",
  "code": "unauthorized"
}
Solana relay
{
  "jsonrpc": "2.0",
  "id": <your id>,
  "error": { "code": -32601, "message": "Method not allowed here." }
}

Status codes

StatusMeaning
400Something in the request is missing or out of range. The message says what.
401Sign in first.
403The CSRF header is missing, the request came from another site, or the feature is not open yet.
404No such coin here (it was not launched on Zpad).
409A conflict, such as a username that is taken.
429Too many requests. See Rate limits.
500Something failed on the server. Nothing was changed.
502pump.fun, PumpPortal or Solana did not answer as expected.
503A source is not reachable just now. Try again in a moment.

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.
Cookies On Our Website. We use cookies to keep you signed in and remember your settings.