name.com Core API (1.2.0)
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.
https://docs.name.com/_mock/coreapi/namecom.api/
https://api.dev.name.com/
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).
- 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/fr
The complete registration requirements for the specified TLD.
General information about a specific TLD. These are not registration requirements, but contain useful information for domain reseller and domain registrants in general.
Whether the TLD supports implementing a Transfer Lock.
Whether there are premium domains for this TLD.
The number of days you have to renew your domain after it has expired, but before it is removed from your account.
The years that a domain is allowed to be registered for.
The registration requirements for this TLD, including required fields, validation rules, and conditional logic.
A detailed description of the registration requirements for this TLD, including eligibility criteria, restrictions, and important notes.
An object containing all required and optional fields for domain registration, with their validation rules and conditional logic.
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, "expirationGracePeriod": 3, "idnLanguages": {}, "allowedRegistrationYears": [ … ] }, "requirements": { "description": "Registration requirements for .fr domains", "fields": { … } } }