Skip to content
einvoicing.dev

Reference

Problems

Every error is application/problem+json (RFC 9457), and its type is a link to one of these pages.

TypeStatusTitle
malformed-body400The request body could not be parsed.
unauthenticated401No valid API key was presented.
allowance-exhausted402The Free plan's monthly allowance is used up.
live-key-required403A test key cannot do this.
not-found404No such resource.
method-not-allowed405That method is not allowed here.
already-subscribed409This account already has a subscription.
no-subscription409This account has no subscription to manage.
sign-in-expired410This sign-in can no longer be used.
payload-too-large413The request body is too large.
unsupported-media-type415This operation does not accept that Content-Type.
unsupported-document422The document is not a Peppol BIS Billing 3.0 invoice or credit note.
unknown-ruleset422There is no such ruleset.
invalid-participant-id422That is not a Peppol participant identifier.
invalid-invoice422The invoice cannot produce a valid Peppol document.
invalid-code422The code is not correct.
invalid-challenge422The proof-of-work challenge was not accepted.
invalid-request422The request body was rejected.
rate-limited429Too many requests.
internal-error500Something went wrong on our side.
upstream-unavailable502The Peppol network could not be asked.
sign-ins-unavailable503Sign-ins are paused.
validator-unavailable503The validator could not judge the document.
request-failedvariesThe request could not be completed.