Undo Customer Merge
POST/api/v2/customers/merge-logs/:mergeLog/undo
Reverse a previous customer merge: un-archives the secondary customer and moves the records that were reassigned during the merge back to it.
customers:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
A merge can only be reversed once, and only within 30 days of the original merge; attempting to reverse an already-reversed or expired merge fails. Use the merge_log_id returned by Merge Customers as the path parameter.
Authentication: Requires Bearer token with the customers read/write scope and the customer merge permission.
Request
Responses
- 200
- 401
- 403
- 404
- 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.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.