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/
- Mock server
https://docs.name.com/_mock/coreapi/namecom.api/core/v1/notifications
- Testing
https://api.dev.name.com/core/v1/notifications
- 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/notifications
{ "subscriptions": [ { … } ] }
The list of configured webhooks you can subscribe to
- Mock server
https://docs.name.com/_mock/coreapi/namecom.api/core/v1/notifications
- Testing
https://api.dev.name.com/core/v1/notifications
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
-u <username>:<password> \
https://docs.name.com/_mock/coreapi/namecom.api/core/v1/notifications \
-H 'Content-Type: application/json' \
-d '{
"eventName": "domain.transfer.status_change",
"url": "https://example.com",
"active": true
}'
{ "subscription": { "active": true, "createDate": "string", "eventName": "string", "id": 0, "updateDate": "string", "url": "string" } }
- Mock server
https://docs.name.com/_mock/coreapi/namecom.api/core/v1/notifications/{id}
- Testing
https://api.dev.name.com/core/v1/notifications/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X DELETE \
-u <username>:<password> \
'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/notifications/{id}'
- Mock server
https://docs.name.com/_mock/coreapi/namecom.api/core/v1/notifications/{id}
- Testing
https://api.dev.name.com/core/v1/notifications/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
-u <username>:<password> \
'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/notifications/{id}' \
-H 'Content-Type: application/json' \
-d '{
"url": "https://example2.com",
"active": false
}'
{ "subscription": { "active": true, "createDate": "string", "eventName": "string", "id": 0, "updateDate": "string", "url": "string" } }
The request sent to your server.
The updated status of the domain transfer. The transfer status will be one of the following values:
- canceled: The transfer has been canceled by the user.
- canceled_pending_refund: The transfer has been canceled by the user, and a refund for the price is being processed.
- completed: The transfer has completed.
- failed: The transfer has failed, and will not be retried.
- pending: The transfer has been requested, and is pending.
- pending_insert: The transfer has completed and the domain will soon be inserted into the account.
- pending_new_auth_code: A new authcode is required to complete the transfer.
- pending_transfer: The transfer has been requested, and is pending.
- pending_unlock: The domain to be transferred is currently in a locked state at the losing registrar, and will begin processing once the lock has been removed.
- rejected: The transfer has been rejected at the losing registrar and will not be retried.
- submitting_transfer: The transfer has been initiated and will soon be submitted to the registry.
- Mock server
https://docs.name.com/_mock/coreapi/namecom.api/domainTransferStatusChange
- Testing
https://api.dev.name.com/domainTransferStatusChange
{ "eventName": "string", "domainName": "string", "status": "string" }