conflict
HTTP 409 Conflict
A resource with the same unique identifier already exists (e.g., duplicate slug or idempotency key collision).
PATCH /v1/codes/:id also answers 409 when other requests changed the same code during every save attempt. Reload the code and send the change again.
POST and DELETE /v1/codes/:id/logo also answer 409 when another request changed the same code’s logo at the same moment. They then change nothing.
DELETE /v1/account also answers 409 when no person is linked to the key (created_by = 'system'). It then deletes nothing; use a key the person created, or request the erasure by e-mail.
POST /v1/dpp, POST /v1/dpp/batch and POST /v1/dpp/import also answer 409, with the title GTIN Verified by Another Organization, when another organization verified the GTIN or its GS1 Company Prefix. The refused GTINs are in gtins (at most 20; total counts all of them); nothing is created, for batch and import not partially either. See GS1 Identifiers & Onboarding.
POST /v1/dpp/:id/register also answers 409, with the title GTIN Held by Another Organization, when the organization of the passport does not hold its GTIN: another organization verified it or created a passport for it first. The GTIN is in gtins; nothing is submitted. See GS1 Identifiers & Onboarding.
DELETE /v1/gs1/identifiers/:id also answers 409 (reason: "verified") when the identifier is verified; only qr3 gives up a verification, by revoking it. PUT and DELETE /v1/files/:id answer 409 (reason: "gs1_verification_proof") when the file is the proof of a GS1 verification request that is under review or approved. See GS1 Identifiers & Onboarding.
POST /v1/gs1/identifiers also answers 409 when your organization has already registered the identifier: reason: "already_registered" (in this workspace) or "registered_in_other_workspace" (in another one; workspace names it if you may open it). A removed identifier, on the other hand, is registered again, unverified. POST /v1/gs1/verifications answers 409 with reason: "request_pending" when a request is already under review; workspace and request_id name it if you may open its workspace. See GS1 Identifiers & Onboarding.