GoDaddy integration: your domain's DNS, without guesswork
A key and secret pasted once, a readable change plan and a cutover you confirm.
With a GoDaddy API key and secret, Pilotiko can inspect your domain, read its DNS, replace the website records during a cutover you confirm and then verify the result. Status: Being commissioned: the connector is written and tested against a test server; it has not yet been verified with a real account.
In short
- GoDaddy has no one-click authorization for DNS, so you create a key and secret.
- The connector knows both GoDaddy's production environment and its OTE test environment.
- GoDaddy's current documentation describes a different token type, so a real-account test is needed.
- Without API access, Pilotiko gives you the exact changes to make yourself.
What does the GoDaddy connection do?
It lets Pilotiko work directly in your GoDaddy DNS zone, so you don't have to copy values by hand from one screen to another.
Plenty of small Canadian businesses bought their domain at GoDaddy and left the DNS there. For a new Pilotiko-hosted site to answer at your address, a few records must change. Pilotiko's GoDaddy connector can authenticate the key, inspect the domain, read its records, replace or delete the ones that serve the website and verify that the change took.
The connector was written for the key-and-secret pair of the Domains API, with a production address and an OTE test address. GoDaddy's getting-started page, read on October 15, 2026, now describes a personal access token sent in a header, with every request going to production [1]. The same page notes that a 403 response can mean the account is not eligible [1], and the Domains v3 reference also shows token-based authentication [2]. Plainly put: the connector has to be checked against a real account, and may need changes, before it can be called available.
- Credentials requested: a GoDaddy key and secret (at least 8 characters each), checked locally before any network call.
- Read: the domain's status and all of its DNS records.
- Written: only the bare-domain and www records, during the cutover.
- Never touched: GoDaddy mailboxes, billing or domain renewal.
- Needs your approval: switching the domain over to Pilotiko.
How do you connect GoDaddy to Pilotiko?
- 1
Create a key at GoDaddy
On developer.godaddy.com, create a key for the Production environment.
- 2
Keep the key and secret together
Pilotiko needs both values.
- 3
Paste them once into Pilotiko
At the "Access the domain's DNS" step of the transition flow, pick GoDaddy. The values are checked, encrypted and never shown again.
- 4
Read the change plan
Pilotiko lists your current records, the ones it proposes to replace and any email warnings.
- 5
Confirm the cutover
Nothing changes at your address until you confirm this manual step.
What is available, being commissioned or coming soon?
| Feature | Status | Detail |
|---|---|---|
| DNS instructions to apply yourself | Available | Exact change list, then "I made the change" |
| Key-and-secret authentication | Being commissioned | Tested against a fake server; GoDaddy docs now describe a token |
| Reading the domain and its records | Being commissioned | Snapshot taken before any change |
| Replacing the website records | Being commissioned | TTL lowered to 600 seconds before cutover |
| Buying, renewing or transferring a domain | Coming soon | No registrar connected |
| GoDaddy email (mailboxes, forwarding) | Coming soon | Not built; never modified |
How many records does a GoDaddy cutover touch?
Who can see your credentials, and how do you cut off access?
The key and secret are encrypted at rest (AES-256-GCM) and never leave Pilotiko's server. Quebec's private-sector privacy act requires security measures suited to the sensitivity of the information (s. 10) and requires informing people of their rights of access and correction and of their right to withdraw consent (s. 8) [3]. To exercise your rights with Pilotiko, see your rights.
Cutting off access: Disconnect in Pilotiko erases the credentials and leaves an entry in the audit log. At GoDaddy, delete the key in your developer account and it stops working everywhere.
What are the GoDaddy-specific limits?
DNS at Cloudflare instead? See the Cloudflare integration. To send from your own address, see Zoho Mail or Gmail. Old site on WordPress: WordPress reader. Overview: integrations.
- Eligibility: GoDaddy says a 403 can mean the account is not eligible for the API [1]. If that happens, Pilotiko switches to instructions you apply yourself.
- Token type: the current documentation describes a personal access token while the connector uses a key and secret. The first real test will settle the gap.
- The OTE environment is for testing; your real records are never changed from OTE.
- Email hosted at GoDaddy is never modified by Pilotiko; if it shares the website's server, the cutover stays blocked until that is fixed.
Frequently asked questions
Why does GoDaddy need a key instead of a Connect button?
GoDaddy offers no one-click authorization for DNS management. You create a key and secret in your developer account and paste them into Pilotiko once.
Is my GoDaddy account eligible for the API?
We can't guarantee it. GoDaddy says a 403 refusal can mean the account isn't eligible, in which case Pilotiko gives you the changes to make by hand.
Can Pilotiko renew my domain?
No. Buying and renewing domains is coming soon: no registrar is connected. Your domain stays yours, at GoDaddy.
What does Pilotiko check before touching DNS?
It saves every record, lowers the TTL to 600 seconds and checks the MX record and mail aliases. Any blocking warning must be fixed before the cutover.
Can I go back to my old site?
Yes. The reverse plan restores the records saved in the snapshot, and propagation then follows each record's TTL.
What is the OTE environment for?
It is GoDaddy's test environment. The connector can use it for testing without touching your real records.
Sources
- GoDaddy Developer, Quickstart for API users (accessed on October 15, 2026).
- GoDaddy Developer, Domains API reference (accessed on October 15, 2026).
- LégisQuébec, Act respecting the protection of personal information in the private sector (CQLR, c. P-39.1) (accessed on October 15, 2026).
Read next
Pilotiko integrations
Google Calendar, Outlook, Zoom, Stripe, LinkedIn, Cloudflare, Twilio and more: what each Pilotiko connection does today, with its status read from the code.
Cloudflare integration: your DNS, handled with a scoped token
Connect your Cloudflare zone to Pilotiko with a token limited to one domain's DNS: snapshot first, email safety checks and an exact rollback plan built in.
Zoho Mail and Pilotiko: an account connection, with no sending yet
Linking a Canada-hosted Zoho Mail account to Pilotiko: scopes requested, what doesn't happen yet, what's stored, and how to revoke access whenever you like.