Merge Duplicate Customers
POST/api/qbo/customers/merge
Merge one QuickBooks Online customer (the secondary) into another (the primary).
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
This endpoint modifies data in QuickBooks itself and is irreversible. QuickBooks has no native merge or unmerge, so the merge is performed by deactivating (soft-deleting) the secondary customer in QuickBooks Online. The secondary customer cannot be restored through this API afterwards.
What happens, in order:
- Both customers are re-fetched from QuickBooks to obtain a fresh sync token.
- A snapshot of both records is stored in a merge log for auditing.
- If the secondary customer was linked to a SKU.io customer and the primary was not, the link is moved to the primary.
- The secondary customer is deactivated in QuickBooks and its local synced copy is deleted from SKU.io. (If QuickBooks reports the secondary was already deleted upstream, only the local cleanup is performed.)
Both customers must belong to the same integration instance. QuickBooks refuses to deactivate a customer with a non-zero balance or open transactions; in that case the API returns a 422 with a qbo_customer_has_open_balance error - resolve the balance in QuickBooks and retry.
Authentication: Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.