Retry a domain transfer
POST /api/v2/domains/{id}/actions/retry-transfer
Try a domain transfer into Hostup again. Check transferStatus.actions.canRetryTransfer on GET /api/v2/domains/{id}/lifecycle first. This call does not check the invoice itself. Sent while the invoice for a paid transfer is unpaid, it starts the transfer before payment. Call it only when canRetryTransfer.allowed is true. When the last attempt failed on the EPP code, send the new code as eppCode. It is saved and used in the same call. A code the registry already rejected returns 409 transfer_blocked with epp_code_unchanged in errors[].code. Send force: true to try it once more anyway. Some domain endings need extra details. The call then returns 422 transfer_recovery_required with the form in recovery.fields and a body to complete in recovery.suggestedBody. Fields with target transferDetails go in recoveryValues. A field with target account is changed on the account with PATCH /api/v2/me, for example registrationIdentifier for an identity or tax number. Then retry with profileUpdated: true. When the registry accepts the transfer, the account holder gets an e-mail. The response has the new transferStatus, the next actions and the registry’s messages. There is no job to poll. Read GET /api/v2/domains/{id}/lifecycle to follow the transfer. A .uk transfer uses no EPP code. transferStatus is then registrar_push_request_required (retry first) or registrar_push_required (ask the current provider to change the registrar tag).
Authentication: An API key with the scope write:domains. About keys and scopes
Request
Path parameters
idstringrequireddom_…).Body (optional)
eppCodestring or nullprofileUpdatedbooleanrecoveryValuesobjectrecovery.fields[].key. Each value is a string of at most 500 characters.forcebooleanExample
curl -X POST "https://cloud.hostup.se/api/v2/domains/dom_01hxa3b4c5d6e7f8g9h0j1k2m3/actions/retry-transfer" \ -H "Authorization: Bearer $HOSTUP_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "eppCode": "Xk7#pQ2v-Lm9w" }'curl -X POST "https://cloud.hostup.se/api/v2/domains/dom_01hxa3b4c5d6e7f8g9h0j1k2m3/actions/retry-transfer" \ -H "Authorization: Bearer $HOSTUP_API_KEY" \ -H "Content-Type: application/json"curl -X POST "https://cloud.hostup.se/api/v2/domains/dom_01hxa3b4c5d6e7f8g9h0j1k2m3/actions/retry-transfer" \ -H "Authorization: Bearer $HOSTUP_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "profileUpdated": true }'curl -X POST "https://cloud.hostup.se/api/v2/domains/dom_01hxa3b4c5d6e7f8g9h0j1k2m3/actions/retry-transfer" \ -H "Authorization: Bearer $HOSTUP_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "recoveryValues": { "registryEligibilityAttestation": "YES" } }'Responses
200 The transfer was retried. transferStatus says where it stands. Here it is a string: the kind that GET /api/v2/domains/{id}/lifecycle gives in its transferStatus object. reason and actions sit beside it.
{ "domainId": "dom_01hxa3b4c5d6e7f8g9h0j1k2m3", "transferStatus": "pending_transfer_in_progress", "reason": "Transfer is being processed at the registry.", "preRetryCleanup": { "failedRegistryRecordDeleted": false }, "domainStatusSynced": false, "actions": { "canUpdateEpp": { "allowed": true, "reason": null }, "canRetryTransfer": { "allowed": false, "reason": "Transfer is already in progress at the registry." }, "canRequestFreshEpp": { "allowed": true, "reason": null } }, "registryHistory": [ { "timestamp": "2026-04-27T12:00:00.000Z", "subject": "Transfer started", "contents": "The transfer request was accepted by the registry." } ]}Response fields
domainIdstringtransferStatusstringpending_transfer_in_progress, registrar_push_required, registrar_push_request_required, transfer_failed_at_registry, transfer_not_at_registry, pending_transfer_generic, awaiting_payment, registry_locked_and_epp_invalid, registry_locked, too_new_for_transfer, transfer_error_known, pending_epp_fallback, active, expired, unknown.reasonstring or nullpreRetryCleanupobjectfailedRegistryRecordDeletedbooleandomainStatusSyncedbooleanactionsobjectcanUpdateEppobjectallowedbooleanreasonstring or nullcodestring or nullcanRetryTransferobjectallowedbooleanreasonstring or nullcodestring or nullcanRequestFreshEppobjectallowedbooleanreasonstring or nullcodestring or nullregistryHistoryarray of objecttimestampstring or nullsubjectstring or nullcontentsstring or nullErrors
Errors are Problem Details with a stable code. Branch on the code, not on the text.
| 400 | The body is not valid. |
| 401 | Unauthorized. Authentication is required. |
| 403 | Forbidden. The caller lacks a required scope or does not own the resource. |
| 404 | Not found. The resource does not exist or is not owned by the caller; code is domain_not_found. |
| 409 | The transfer cannot be retried now. transfer_not_in_progress: the domain is not a pending transfer. transfer_blocked: errors[].code names what to fix first: registry_lock (unlock the domain at the current provider), epp_invalid or epp_code_unchanged (get a new EPP code), registrar_fee_confirmation, registrant_not_eligible or unknown. A retry does not fix registrar_fee_confirmation or registrant_not_eligible. Contact support for those. |
| 422 | The transfer needs more details (transfer_recovery_required). Send recovery.suggestedBody back with the empty values filled in. |
| 429 | The domain is still in the transfer lock that follows a recent registration (cooldown_active). Try again when the lock has ended. |
| 500 | Internal error. Retry later or contact support if the issue persists. |
| 502 | The registry or a step before it failed (upstream_failed). detail says what failed. When it says an identity detail already saved on your account could not be used, you do not need to enter it again. Retry later. Contact support if it keeps failing. |