Skip to content

Customer match ambiguous

HTTP 409customer_match_ambiguous

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

Version v1.1, updated

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

On this page

With match_by, more than one customer of the company has the email or registration number of the body. BIRP does not pick one for you.

At a glance

  • Status: 409 Conflict

  • Code: customer_match_ambiguous

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

Causes and fixes

Likely cause

How to fix it

Two customers in BIRP share an email, such as one purchasing address for two companies.

Link the external id to the right customer first, with External references. Then send the upsert again.

match_by uses a value that is not unique among your customers.

Match by registration_number only, or leave match_by out and link the customers yourself.

Example

409 customer_match_ambiguousJSON
{
  "code": "customer_match_ambiguous",
  "detail": "More than one customer matches. Link the external id to one of them first.",
  "errors": [
    {
      "field": "email",
      "message": "matches more than one customer of the company"
    }
  ],
  "instance": "/v1/customers/external/woocommerce/cust-77",
  "request_id": "a1b2c3d4-0000-4000-8000-0000000000ee",
  "status": 409,
  "title": "Customer match ambiguous",
  "type": "https://birp.io/developers/errors/customer_match_ambiguous"
}

Related

  • customers
  • external-references
  • customers-resource