Submit an inbound domain transfer with the Domain Nexus v2 API

1. Confirm the domain is eligible under its registry and registrar policy. Resolve removable locks and any applicable waiting period.
2. Obtain the current EPP or transfer authorisation code when that TLD uses one. Treat it as a secret.
3. Read the active transfer requirements and collect accurate contacts, required fields and consents.
4. Obtain the transfer quote and confirm the intended period and currency.
5. Record the current DNS service and arrange continuity if the old registrar's DNS or email service will end.

Your credential needs domains:transfer. Use JSON and a stored idempotency key. The following shows the main request shape; include the additional fields and contacts required by the current contract.

POST /v2/domains/transfer
Idempotency-Key: transfer-local-order-1042
Content-Type: application/json

{
  "domain": "example.com",
  "years": 1,
  "price_quote_id": "QUOTE_ID",
  "client_reference": "local-order-1042",
  "epp_code": "TRANSFER_CODE_FROM_OWNER"
}

The current field is epp_code. Old parameter names and generic addon arrays are not a substitute for the v2 contract. Never place the real code in logs or a public example.

Save the returned operation reference and follow its state. Read the domain's transfer resource when its identifier is available. Complete any verification requested by the relevant registrar or registry through the authorised channel.

A pending transfer is neither a failed registration nor a reason to submit a registration request. Completion timing and the resulting term depend on the TLD and provider. Check the final domain record and expiry instead of promising a universal number of days or extra years.

For a timeout, inspect the existing operation. For a rejected code or lock, correct the specific issue and follow the supported retry process. Preserve the original request reference so support can establish whether any upstream action occurred.

After completion, verify registrar state, nameservers, DNSSEC and the website and email services you intended to retain. A registrar transfer does not itself copy hosted content or mailboxes.

• Get started with the current Nabtech Domain Nexus v2 API
• Monitor and reconcile a pending domain transfer through the v2 API
• Build domain forms from current registry field and consent requirements
• Create a domain-operation quote and keep its currency and expiry attached to the order
• Transfer an existing domain to us without overlooking DNS or eligibility