Skip to content

External id in use

HTTP 409external_id_conflict

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

Version v1.1, updated

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

On this page

The source and external id you sent already identify another record of the company. One external id of one source identifies one record only.

At a glance

  • Status: 409 Conflict

  • Code: external_id_conflict

  • Retry: No. Fix the cause first: the same request gets the same answer.

Causes and fixes

Likely cause

How to fix it

A create sends an external id that an earlier create already linked.

Read the record with that external id and update it. The upserts by external id create or update in one call.

The order with this source and external_id was already imported.

Read it with GET /v1/orders?source=woocommerce&external_id=order-5512 instead of creating it again.

A link names an external id that another record already holds.

Remove the link from the other record first, with External references.

Example

409 external_id_conflictJSON
{
  "code": "external_id_conflict",
  "detail": "This external id of this source already identifies another record of the company.",
  "instance": "/v1/categories",
  "request_id": "a1b2c3d4-0000-4000-8000-0000000000ee",
  "status": 409,
  "title": "External id in use",
  "type": "https://birp.io/developers/errors/external_id_conflict"
}

Related

  • references-and-external-ids
  • external-references
  • receive-orders
  • sync-products