1. Generate a Personal Access Token
1
Sign in
Sign in to developer.godaddy.com with the GoDaddy account that holds the domains.
2
Generate a token
Generate a Personal Access Token (PAT). Pick the Domains & DNS scopes. Add the Hosting and Email scopes when your agents work on websites and mailboxes. A token without a scope gets a refusal from GoDaddy for that area.
3
Copy it
Copy the token. GoDaddy shows it once.
Optional: the Classic Developer Key
GoDaddy serves SSL certificates, abuse reports, parking, legal agreements, countries and the shopper account only to its older Classic Developer Key. To let agents read certificates (for example in a domain audit), create a Production key at classic-developer.godaddy.com/keys on the same account and copy its key and secret. Neo sends that key only to those APIs, and the token to everything else. GoDaddy lets a token manage domains only on an account that holds at least one domain, and registers or renews a domain only when the account has a payment method or a Good as Gold balance.2. Add the token in Neo
1
Open Integrations
In the Neo Dashboard, open Integrations and find the GoDaddy card, under Other.
2
Save the token
Paste the Personal Access Token, and the Classic Developer Key and its Secret if you made one, and click Save. Neo reads one domain with each before saving, so a wrong token or key, or one without the Domains scope, is reported straight away.
3. Turn GoDaddy on per agent
Open the agent, go to the Tools & Settings tab, and configure the GoDaddy block under Tools & Integrations. Pick a profile, or set each area:
See GoDaddy API for what the agent can do.
