Skip to content

Knowledgebase

Connect DNS Made Easy with its paired API credentials

domain-nexus, development

DNS Made Easy uses an API key and a separate secret key. Domain Nexus needs both values from the same account credential pair. A DNS Made Easy login password or a key from a different account will not produce the required authenticated requests.

01 Find the credential pair

Sign in as the primary DNS Made Easy account user. Open Config, then Account Information, and find or generate the API credentials. API availability depends on the provider's current membership level. If the credential area is absent, verify both the account role and service entitlement before assuming the module is misconfigured.

Keep the pair in your approved credential store and note other integrations that use it. The provider authenticates signed requests, so the server running WHMCS also needs an accurate clock. Avoid diagnosing a time-related signature failure by permanently expanding account permissions.

02 Save the Domain Nexus connection

  1. Add a server with provider DNS Made Easy.
  2. Copy the public identifier into API Key and the matching secret into Secret Key.
  3. Leave API Base URL at the production default for live DNS. Use an alternate sandbox address only when the provider has supplied the corresponding environment and credentials.
  4. Save and check the connection. Assign a test package and verify an owned zone read.
  5. Add and remove one temporary TXT record, inspecting the provider's final record state after each completed task.

Common questions

Can I test against a sandbox and then point customers at it?

A sandbox proves a supported test workflow within that environment. Customer domains need the production service, production credentials and production authoritative nameservers. Recheck those values during the live handover.

Why did changing only the secret stop access?

API credentials are a pair. Check whether a new generation replaced both values, and update every connection that uses them. Compare the WHMCS server's time and any provider access restrictions as well.

If a write fails after authentication, inspect the account's DNS permissions and limits. Preserve the existing zone until the outcome is known rather than deleting and recreating it to force a retry.

Sources and further reading

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support

Powered by WHMCompleteSolution