GoDaddy now uses personal access tokens. They expire, and GoDaddy only answers for accounts that qualify. Both facts are easier to handle if you know about them before you generate one.
Check your account first
GoDaddy responds to API calls only for an eligible account. In practice that means at least one domain on the account to manage domains and DNS, and a payment method on file if you want to buy domains. An account that does not qualify gets a 403 response, whatever the token says.
Generate the token
- Sign in at
developer.godaddy.com/personal-access-token. - Click Generate Token.
- Fill in the form:
- Token Name, for example
dnsense. - Expires After, one of 7, 30, 60 or 90 days, or 1 year.
- Permissions, where you select the Domains & DNS bundle.
- Token Name, for example
- Click Create Token.
- In the Personal Access Token Created dialog click Copy Token. The token is shown once. Store it in a password manager before you close the dialog.
Pick the expiry on purpose
Take the longest one you are comfortable with, which is 1 year. A 7-day token means your connection goes offline every week. Put the expiry date in your calendar anyway. When it nears, generate a new token and replace the credentials on the existing DNSense connection. You do not have to delete and recreate it.
Limits worth knowing
GoDaddy rate-limits per token, currently 600 calls per roughly 23 minutes. DNSense stays under that. Its v3 records API also has no TLSA records and accepts TTLs between 600 and 86400 seconds, so DNSense refuses values outside that range for GoDaddy zones.
Connect it to DNSense
Add a connection, choose GoDaddy and paste the token. That is the only field.