Problems·HTTP 429

rate-limited

Too many requests.

What it means

The request was over a rate limit. For sign-ins this includes the one-minute wait between codes to the same address, which has its own title.

What to do

Wait the number of seconds in the Retry-After header, then retry.

Example

Sent as application/problem+json (RFC 9457). Branch on type, which is stable. Never branch on title or detail, which are prose and may change.

{  "type": "https://www.einvoicing.dev/problems/rate-limited",  "title": "Too many requests.",  "status": 429,  "detail": "…"}

Returned by

• Validate a Peppol document POST /v1/validations
• Convert a JSON invoice to Peppol UBL POST /v1/conversions
• Look up a Peppol participant GET /v1/participants/{participant_id}
• List supported rulesets GET /v1/rulesets
• Get usage for the current billing period GET /v1/usage
• Get a proof-of-work challenge for sign-in POST /v1/sign-in-challenges
• Email a one-time sign-in code POST /v1/sign-ins
• Exchange a one-time code for an API key POST /v1/sign-ins/{sign_in_id}/confirmation
• List API keys GET /v1/keys
• Create an API key POST /v1/keys
• Revoke an API key DELETE /v1/keys/{key_id}
• Get the account GET /v1/account
• Start a subscription POST /v1/billing/checkout-sessions
• Manage a subscription POST /v1/billing/portal-sessions