Common API errors and how to resolve them

successful:false on a 200, missing headers, and other frequent gotchas.

Updated August 31, 2026 · 1 min read

"My request returned 200 but nothing happened"

Cause: the request failed logically, not transport-wise. PTERI wraps every response as { successful, message, data }, and a failure can still be HTTP 200 with successful: false. Check that field before assuming success — see understanding the API response envelope.

"401/403 on every request"

Cause: the nodeUrlOrApiAccessKey header is missing, malformed, or sent with a Bearer prefix it doesn't expect. Send your raw API key (or Enterprise node URL) as the header value directly.

"Address creation fails"

Cause: POST /api/Address/create requires both the target walletName and an encryptedPassphrase header — a common mistake is sending one without the other.

Still stuck?

Submit a ticket under Technical / API with the exact request you sent (redact your API key) and the full response body.

Still stuck?

Ask Kai about this article, or open a ticket with our team.

Submit a ticket