Errors

All Manka error responses share a single JSON shape:

{
  "message": "Human-readable error description"
}

The HTTP status code is the primary signal — the message field is a hint for humans and may change between releases.

Status codes

Status	Category	Typical cause
`400`	Bad request	Missing required field, unreadable PDF, or password required and not supplied
`401`	Unauthorized	Missing or invalid API token
`402`	Payment needed	Account has no remaining analysis credits
`404`	Not found	Task ID is unknown or has expired (24 h TTL)
`500`	Server error	Internal error processing the request
`503`	Unavailable	Underlying datastore is unreachable

Handling errors

401 — Unauthorized

Verify the Authorization header is present and the token has not been revoked or rotated. Generate a fresh token from Developer Tools.

402 — Insufficient credits

Each call to /analysis, /transactions, or /analysis-combined deducts one credit. Check your balance on the Manka dashboard or contact support to top up.

400 — Password protected PDF

Re-submit with the password field set. For /analysis-combined, pass a JSON array via passwords positionally matching the files.

404 — Task not found

Task records expire 24 hours after creation. Re-submit the statement if you still need a result.

Example

401 Unauthorized

{ "message": "Invalid API token" }

402 Payment Required

{ "message": "Insufficient analysis credits" }

Getting Started

Reference

Status codes

Handling errors

Example

​Status codes

​Handling errors

​Example

Status codes

Handling errors

Example