Skip to content

Internal error

internal_error

When the API answers 500 internal_error, and how to fix it.

Version v1.1, updated

The type field of every internal_error response links to this page.

On this page

Something failed on the side of BIRP while it handled the request. The request itself was not at fault.

At a glance

  • Status: 500 Internal Server Error

  • Code: internal_error

  • Retry: Yes, a few times, with a growing wait and the same idempotency key.

Causes and fixes

Likely cause

How to fix it

A passing failure on the side of BIRP.

Retry a few times, with a growing wait. Keep the same idempotency key, so a write is never applied twice.

The failure repeats for the same request.

Write to BIRP support with the request_id and the time of the request. Never send the API key.

Example

500 internal_errorJSON
{
  "type": "https://birp.io/developers/errors/internal_error",
  "title": "Internal error",
  "status": 500,
  "detail": "An unexpected error occurred. Quote the request id when contacting support.",
  "instance": "/v1/invoices",
  "code": "internal_error",
  "request_id": "a1b2c3d4-0000-4000-8000-0000000000ee"
}

Related

  • handling-errors
  • idempotency
  • errors-overview