GidiNET
GidiNET API credentials setup: generate GidiNET's separate API password and pair it with your normal account username for DNS and nameserver operations.
On this page
GidiNET API credentials permissions
- Credential type
- Username and API password
- Preview access
- domainGetList, domainInfo, and recordGetList
- Apply access
- recordAdd, recordUpdate, recordDelete, and domainNameServersChange
- API endpoint
- DNSMigrator uses the provider's fixed API endpoint.
Additional access
DNSControl id
{
"TYPE": "GIDINET"
}Create credentials
Generate GidiNET's separate API password and pair it with your normal account username for DNS and nameserver operations.
Access you'll grant
domainGetList, domainInfo, and recordGetList
recordAdd, recordUpdate, recordDelete, and domainNameServersChange
Before you start
- A GidiNET account containing the active domains you want to manage.
- API nameserver-change access on the account; this may require a reseller-enabled account.
Setup steps
0 of 4 done
Open the account password page
Sign in to the GidiNET members' area, then open Configuration → Change password. Use the account's API-password control; the public page does not expose the authenticated form labels.
Generate an API password
Create a dedicated API password. It is separate from the password used to sign in to the control panel and can be replaced independently.
Copy your account username
Use the same account identifier you normally enter in GidiNET's Username field. Do not substitute a domain name or contact handle.
Enter the API credentials
Paste the account login into Username and the dedicated secret into API password, then check access.
Troubleshooting
GidiNET reports an authentication error
Use the normal account username together with the separate API password. Regenerate the API password if it was copied from the login-password field.
A domain is missing
The API lists active domains in this account. Confirm the domain is active and belongs to the username you connected.
A nameserver change is forbidden
The account may not have registrar API access. Ask GidiNET whether CoreAPI domainNameServersChange is enabled for the account.
DNSSEC cannot be changed
The GidiNET connection has no DS-record API. Handle DNSSEC in the registrar's control panel before or during cutover.
Official documentation
Guide checked against the official documentation on .
Credential fields
| Field | Requirement | Where to find it |
|---|---|---|
| Usernameusername | Required | Your normal GidiNET members-area username. |
| API passwordpassword | Required | The dedicated API password generated in the account, not the members-area login password. |
Capabilities
- Create zones
- No
- List zones
- Yes
- DNSSEC
- Not available through this connection
- Minimum TTL
- 60 seconds
- Apex CNAME
- No
- Read only
- No
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
Caveats
- TTLs are limited to fixed steps (60 s to 2 days); other values are rounded up to the next allowed step.
- CAA records are only available on the premium DNS service and aren't managed by DNSMigrator.
- Apex NS records and read-only system records can't be changed through the API.
Troubleshooting
- GidiNET reports an authentication error
- Use the normal account username together with the separate API password. Regenerate the API password if it was copied from the login-password field.
- A domain is missing
- The API lists active domains in this account. Confirm the domain is active and belongs to the username you connected.
- A nameserver change is forbidden
- The account may not have registrar API access. Ask GidiNET whether CoreAPI domainNameServersChange is enabled for the account.
- DNSSEC cannot be changed
- The GidiNET connection has no DS-record API. Handle DNSSEC in the registrar's control panel before or during cutover.