easyname
easyname API key setup: activate easyname API access and copy the user identity, API key, authentication salt, and signing salt used to authorize nameserver changes.
On this page
easyname API key permissions
- Credential type
- API key and two salts
- Preview access
- GET /domain for the account's active domains and current nameservers
- Apply access
- POST /domain/<id>/nameserverchange
- API endpoint
- DNSMigrator uses the provider's fixed API endpoint.
Additional access
DNSControl id
{
"TYPE": "EASYNAME"
}Create credentials
Activate easyname API access and copy the user identity, API key, authentication salt, and signing salt used to authorize nameserver changes.
Access you'll grant
GET /domain for the account's active domains and current nameservers
POST /domain/<id>/nameserverchange
Before you start
- An easyname account eligible for its professional or commercial API.
- The account's exact numeric user ID and current email address.
Setup steps
0 of 5 done
Open API access
Sign in to easyname and open Account → API. The API must be activated before credentials are issued.
Activate the API
Enable API access for the account. easyname's public reference says this interface is provided for professional and commercial users; contact support if the activation control is unavailable.
Copy the API secrets
Copy API key, API authentication salt, and API signing salt exactly as shown. The authentication salt must retain both
%smarkers.Authentication-salt shapeprefix%sbetween%ssuffixCopy the account identity
Record the numeric User ID and the account's current Email value. easyname inserts both into the authentication salt, so an email change also changes the derived authentication value.
Enter all five values
Paste the values into User ID, Account email, API key, API authentication salt, and API signing salt, then check access.
Troubleshooting
The authentication salt is rejected
Paste the original value with exactly two %s markers. Do not replace those markers yourself.
Authentication stopped after an email change
Update Account email in DNSMigrator to the exact current easyname account email; it is part of the authentication hash.
A nameserver change remains pending
easyname can queue registry operations. Wait for the existing domain update to complete before retrying.
More than six nameservers are requested
The easyname API exposes nameserver1 through nameserver6. Reduce the destination set to no more than six.
Official documentation
Guide checked against the official documentation on .
Credential fields
| Field | Requirement | Where to find it |
|---|---|---|
| User IDuserId | Required | The numeric user/customer ID displayed for the easyname account. |
| Account emailemail | Required | The account email address exactly as registered. It is part of the authentication hash and must be updated here when it changes. |
| API keyapiKey | Required | The API key issued after API access is activated. |
| API authentication saltauthSalt | Required | The API authentication salt. Paste it unchanged; it must contain two literal %s markers for user ID and email substitution. |
| API signing saltsignSalt | Required | The API signing salt used to sign POST requests such as nameserverchange. |
Caveats
- Up to 6 nameservers per domain.
- Only nameservers can be changed through the API; DNSSEC is managed in the dashboard.
Troubleshooting
- The authentication salt is rejected
- Paste the original value with exactly two %s markers. Do not replace those markers yourself.
- Authentication stopped after an email change
- Update Account email in DNSMigrator to the exact current easyname account email; it is part of the authentication hash.
- A nameserver change remains pending
- easyname can queue registry operations. Wait for the existing domain update to complete before retrying.
- More than six nameservers are requested
- The easyname API exposes nameserver1 through nameserver6. Reduce the destination set to no more than six.