Responses and errors

Every response uses the same envelope. Check the HTTP status first, then the body.

The envelope

{
  "message": "License verified successfully",
  "code": "00",
  "success": true,
  "data": { }
}
successboolean
True for 2xx responses.
codestring
00 on success, 01 on error.
messagestring
A short summary, such as NOT_FOUND on errors. Don’t match on its wording; it can change.
dataobject | null
The result on success; null on error.
errorobject | null
On error, details explains what went wrong.

Status codes

StatusMeaningWhat to do
200It worked.Use data.
400The request is malformed or a value is invalid.Fix the request; don't retry as is.
401Missing, revoked or expired secret key.Check the key and its environment.
402Not enough credits.Ask the user to top up; don't retry.
403Not allowed, for example a frozen wallet.Don't retry.
404The licence, app user key or wallet wasn't found for your organisation.Treat as not entitled.
409Already exists, for example a reused idempotency key.Treat a usage retry as recorded.
500Something failed on Ploba's side.Retry with backoff, reusing the same idempotency key.

Last updated Oct 9, 2026Report a problem with this page