A duplicate detection error means the request would create a record or value that must be unique, but a matching one already exists. The request is rejected to protect data integrity.
Every error in this family includes a stable code (for example BIZL-1001). Find that code in the table at the bottom of this article to see exactly which rule was triggered.
Common causes
A create request was sent for something that already exists.
The payload contains duplicate entries in a list.
An External ID or key is already mapped to another record.
A retry re-sent a create that already succeeded.
How to fix it
Match the code in your response to the table below.
Check whether the record already exists with a GET request.
If it exists, use an update (PUT) instead of a create (POST).
Remove duplicate entries from the request payload.
Re-send the request.
Codes in this family
Code | What it means |
| Duplicate {fieldOrObjectName} found on the {apiName} request. |
| Duplicate {childObject} found while trying to create or update {parentObject}. {childObject} must be unique (Id: {id}). |
| External Id must be unique and the provided one ({externalId}) already exists. |
| {field name} must be unique and there is already an item (ID: {id}) using that value. |
| Duplicate external id found on the {tableName} request. External Ids per system must be unique. |
| {field} must be unique and {value} is already in use. |
| {object} do not support duplicate entries. |
| {dataType} (Id: {id}) already exists. |
| Combinations of Alternate IDs and Units must be unique and the combination provided (Alternate ID:{id} | Unit ID:{unitId}) is already in use. |
| Only one related product can exist per {scope} (SKU: {sku}|Related Id: {relatedId}|Related Type: {relatedType}). |
| Kit components must be unique per kit and a component with sku {sku} has already been added to this kit. |
| An OAuth entry already exists with the key {callbackEntry.IdentificationKey}. Please delete the existing entry before retrying. |
| Employee email must be unique and there is already an employee using the email {email}. |
| There is already an active CompanyPlanActivePromo ({promoId}) for this company ({companyId}). |
| Payment must be unique per transaction (Transaction Id:{transactionId}, Status:{status}, Amount:{amount}). |
| Tax must be unique per transaction (Transaction Id: {transactionId}, Authority: {authority}, Amount: {amount}). |
| Duplicate custom field ({customFieldName}) found while trying to create or update {parentObject}. Custom fields must be unique on each request. |
| Tracking number must be unique and {trackingNumber} is already in use on this transaction. |
| Another user at your company ({companyId}) has already accepted the {documentType}. |
| Integration version must be unique and {versionId} is already in use. |
| Marketing Info must be unique and ({id}) already exists. |
| Plan Email ({planId}, {emailTemplateId}) already exists. Use PUT to update the existing record! |
| There is a duplicate quota check on this company {companyId} with the same values (Type: [checkType}, Time: {checkDateTime}) |
| Enhancement names must be unique and ({name}) already exists. |
| Role names must be unique and {request.Name} is in use by another role. |
| An enhancement can only exist on once on a plan and enhancement Id {enhancementId} is already in use. |
| Note must be unique and there is already an item (Note Text: {noteText}) using that value. |
| Duplicate Parameter (Name:{name}) found on request. |
| Table names must be unique and there is already one named {tableName} (Id: {Id}). |
| A company is not allowed to subscribe to the same enhancement multiple times. This company ({companyId}) is already subscribed to this enhancement ({enhancementId}). |
| Category sets must be unique and there is already a duplicate (Id = {id}). |
| Variant SKUs must be unique and SKU {sku} is already in use on this product. |
| The combination of External Id and Subscription Id must be unique. |