What you'll need

A name.com account that owns (or manages) the domains you want to sync.

Permission to use Domain Manager → Registrants in NIZU (Settings access).

Two pieces of information from name.com: your API username and an API token.

Step 1 — Create your name.com API token

name.com occasionally updates its dashboard, so the exact labels may differ slightly. The goal is to reach the API token area of your account settings.

1. Log in at name.com.
2. Open your Account → API settings (look for API Tokens / API for name.com).
3. Create a new API Token.
4. Note down:
5. Your API username — usually your name.com account username.
6. The API token — a long secret string. Copy it now; name.com shows it only once.

Sandbox (optional, for testing): name.com offers a separate test environment with its own accounts and tokens. If you want to trial Domain Manager without touching live domains, create a sandbox account and token at name.com's developer/sandbox site, and choose Sandbox as the environment in Step 2.

Step 2 — Add the registrant in NIZU

1. In NIZU, go to Domain Manager → Registrants.
2. Click Add Registrant.
3. Fill in the form:
4. Field What to enter
5. Title A friendly label, e.g. "name.com — main account".
6. Provider name.com.
7. Environment Production for live domains, or Sandbox for testing.
8. API Username Your name.com API username from Step 1.
9. API Token The API token you copied from Step 1.
10. Status Active.
11. Click Test Connection.
12. ✅ Success means NIZU reached name.com with your credentials.
13. ❌ Failure usually means a wrong username, token, or environment — re-check and try again.
14. Click Save.

About the token: it's stored securely and never shown again. When you edit this registrant later, leave the token field blank to keep the existing one, or enter a new token to replace it.

Step 3 — Sync your domains

Open Domain Manager → Domains.

The list syncs automatically, pulling your domains from name.com along with their expiry dates and status.

You'll see a short summary of what was checked, synced and created.

From here you can manage DNS records and nameservers for any synced domain — every change is sent to name.com in real time. See How to Use Domain Manager.

1. Production vs Sandbox — which to pick
2. Production Sandbox
3. Purpose Real domains and live changes Safe testing and training
4. name.com endpoint api.name.com api.dev.name.com
5. Credentials Your live name.com account A separate sandbox account
6. Use when You're ready to manage real domains You're trialing the workflow
7. Troubleshooting
8. "Test Connection" fails.
9. Confirm the API username is correct (it's your name.com username, not your email).
10. Re-copy the API token — they're long and easy to truncate.
11. Make sure the Environment matches the credentials (production token with Production, sandbox token with Sandbox).
12. Check that your name.com account has API access enabled.
13. Domains don't appear after connecting.
14. Make sure the registrant Status is Active.
15. Re-open the Domains list to trigger another sync.
16. Confirm the domains are actually held in that name.com account.
17. A DNS or nameserver change was rejected.

The change is only saved in NIZU if name.com accepts it. Read the error message, fix the record (e.g. an invalid value or a duplicate), and try again.

For DNS, remember a domain needs valid records; for nameservers, at least two are required.

I need to rotate the API token.

Create a new token at name.com, then edit the registrant in NIZU and paste the new token (leaving it blank keeps the old one). Test the connection again.