1. Read the exact owned domain and confirm the business reason for the account move.
2. Verify the intended destination reseller through the authorised account workflow. This route expects its numeric to_reseller_id, which is different from a domain public ID or an end-customer email address.
3. Review pending orders, billing responsibility, DNS access and customer contacts that may be affected.
4. POST the destination ID and a clear reason, using the required idempotency key.
5. Store the returned request reference and follow the operator's review or approval process.
6. After completion is independently confirmed, re-read the domain from the appropriate authorised account and verify its management access.

No. Another installed extension may expose its own client-account push workflow. This Domain Nexus API route records a reseller ownership-transfer request and must be documented according to that actual behaviour. Do not promise immediate transfer or assume another extension's conditions apply.

No registrant change is implied by this request. Registry contact updates have their own operation and verification rules. A reseller account can manage registrations for end customers whose legal registrant data remains separate.

Stop and review the pending request through the authorised support or administrative workflow. Do not send a second opposite-direction request as an assumed rollback. Preserve the original reference and explain the intended recipient.

Before retiring the source integration's access, confirm that the approved move, billing responsibilities and any DNS entitlements are complete. Account ownership, authoritative DNS and registry sponsorship should each be verified against their own records.

• Move a domain to another your client account
• Keep end-customer registration contacts separate from reseller account ownership
• Update domain contact roles with the current v2 API
• Track domain orders and cancel only work that remains cancellable