RESTful API for managing domains, DNS records, and related services at name.com. Access via HTTPS at api.name.com (production) or api.dev.name.com (testing). Supports standard authentication, rate-limited to 20 requests/second.
name.com Core API (1.8.2)
Download OpenAPI description
Overview
Account Services
Languages
Servers
Mock server
https://docs.name.com/_mock/coreapi/namecom.api/
Testing
https://api.dev.name.com/
Contact Verification
Use Contact Verification endpoints to query a reseller’s unverified domains/emails and to programmatically mark an end user’s email as verified if the reseller has already completed the verification process. These endpoints help resellers meet ICANN requirements by ensuring end users confirm they can receive email at their listed address.
Operations
Request
Returns the registration requirements some general information for a specific TLD. The response contains a detailed description of eligibility criteria and a fields object with all required and optional fields, including validation rules, conditional logic, and nested field structures. Provide the TLD as a path parameter to retrieve its complete registration requirements. Useful when you only need details for one TLD (e.g., when a user selects .fr from a dropdown).
Security
BasicAuth
- Mock server
https://docs.name.com/_mock/coreapi/namecom.api/core/v1/domaininfo/requirements/{tld}
- Testing
https://api.dev.name.com/core/v1/domaininfo/requirements/{tld}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
-u <username>:<password> \
https://docs.name.com/_mock/coreapi/namecom.api/core/v1/domaininfo/requirements/frThe complete registration requirements for the specified TLD.
Whether the TLD supports implementing a Transfer Lock.
Example: true
Whether there are premium domains for this TLD.
Example: true
Whether this TLD requires pre-delegation. If this is true, these domains must be added to the name servers before the domain creation is completed.
Example: true
The number of days you have to renew your domain after it has expired, but before it is removed from your account.
Example: 25
The years that a domain is allowed to be registered for.
Example: [1,3,5,8,10]
The IND Languages that the TLD supports (if any).
Example: {"DE":"German","DK":"Danish","ES":"Spanish","IT":"Italian","JP":"Japanese"}
The entire TLD namespace has been added to the HSTS Preload list. As such, all second-level domains under .TLD will only load on modern browsers if a valid SSL certificate has been configured and the webserver is serving HTTPS.
Example: true
The minimum allowed length for the second level domain (SLD) for a given TLD. The SLD would be the example part of example.com. Attempts to register a domain with a shorter length than allowed will result in a failure of a Create Domain request.
Example: 3
The minimum allowed length for the second level domain (SLD) that utilizes an IDN character for a given TLD. The SLD would be the èxample part of èxample.com. Attempts to register a domain with a shorter length than allowed will result in a failure of a Create Domain request. This value will often be different from the minDomainLength for non-IDN registrations. This parameter will return as null for any TLDs that do not support IDN registrations.
Example: 5
A detailed description of the registration requirements for this TLD, including eligibility criteria, restrictions, and important notes.
Example: "Required fields to register an .fr domain"
Response
application/json
Example of a complex requirement set with multiple fields, conditional logic, and nested requirements
{ "tldInfo": { "tld": "fr", "ccTld": true, "supportsTransferLock": true, "supportsDnssec": true, "supportsPremium": true, "supportsPrivacy": true, "requiresPreDelegation": true, "expirationGracePeriod": 3, "idnLanguages": {}, "allowedRegistrationYears": [ … ], "hsts": false, "minDomainLength": 5, "minIdnDomainLength": 5 }, "requirements": { "description": "Registration requirements for .fr domains", "fields": { … } } }