Check registrant change requirements
Retrieves the requirements of a registrant change.
Path parameters
The account id
Request body
Example request
{
"domain_id": "dnsimple.com",
"contact_id": "2"
}Response
Successfully returned the registrant change requirements.
Example response
{
"data": {
"contact_id": 2,
"domain_id": 2,
"extended_attributes": [
{
"name": "x-fi-registrant-birth-date",
"title": "The registrant's birth date",
"description": "Format is: YYYY-MM-DD.",
"required": false,
"options": []
}
],
"registry_owner_change": false
}
}Changes
Changed in 3 of the 54 revisions of this API.312
- ▲
the request property
became requiredrequest-property-became-required
- ▲
the request property
became requiredrequest-property-became-required
- ○
the response property
became required for the statusresponse-property-became-required
- ○
the response property
///became required for the statusresponse-property-became-required
- ○
the response property
///became required for the statusresponse-property-became-required
- ○
the response property
///became required for the statusresponse-property-became-required
- ○
the response property
/////became required for the statusresponse-property-became-required
- ○
the response property
/////became required for the statusresponse-property-became-required
- ○
the response property
/////became required for the statusresponse-property-became-required
- ○
the response property
///became required for the statusresponse-property-became-required
- ○
the response property
became required for the statusresponse-property-became-required
- ○
the response property
became required for the statusresponse-property-became-required
- ○
added the required property
///to the response with the statusresponse-required-property-added
- ▲
- ○
endpoint added
endpoint-added
- ○
- ▲
api path removed without deprecation
api-path-removed-without-deprecation
This revision also has 25 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲