Skip to content

Numbering busy

HTTP 409numbering_conflict

When the API answers 409 numbering_conflict, and how to fix it.

Version v1.1, updated

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

On this page

BIRP could not give the number this time. Your request was not applied, so you can send it again.

At a glance

  • Status: 409 Conflict

  • Code: numbering_conflict

  • Retry: Yes, at once, with the same key.

Causes and fixes

Likely cause

How to fix it

The number could not be given at this moment.

Retry at once with the same idempotency key.

Example

409 numbering_conflictJSON
{
  "code": "numbering_conflict",
  "detail": "The numbering series was busy. Retry the request.",
  "instance": "/v1/invoices/00000000-0000-4000-8000-000000000061/issue",
  "request_id": "a1b2c3d4-0000-4000-8000-0000000000ee",
  "status": 409,
  "title": "Numbering busy",
  "type": "https://birp.io/developers/errors/numbering_conflict"
}

Related

  • invoices
  • handling-errors
  • idempotency