-
Notifications
You must be signed in to change notification settings - Fork 69
Open
Description
I’m trying to automate domain provisioning using GoDaddy API.
I can successfully update nameservers via:
PATCH /v1/domains/{domain}
But hostname (glue) creation fails:
POST /v1/domains/{domain}/hosts - 404
PATCH /v1/domains/{domain}/records - 422
Even after:
- Forcing default GoDaddy nameservers (ns01/ns02.domaincontrol.com)
- Waiting 30+ minutes
- Retrying API
However, the SAME hostname creation works instantly in GoDaddy UI:
ns1.example.com → IP
ns2.example.com → IP
After manually creating hostnames in UI, API allows setting nameservers.
So effectively:
- NS change via API works
- Hostname creation via API blocked
- UI hostname creation works
This blocks full automation.
Questions:
- Is glue/hostname creation restricted by account tier?
- Is there any way to enable it via API?
- Is there a supported automation workaround?
Environment:
- GoDaddy REST API v1
- .com domains
- Portfolio / reseller style account
- Auth via sso-key
Expected:
If hostname creation is allowed in UI, it should also be allowed via API, or at least return clear permission errors instead of 404/422.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels