Modifying a Contact
Synopsis
| Description | A command to modify a contact object |
| URL | https://toolkit.centralnic.com/srv/modify_handle |
| HTTP Method | POST |
| Requires Authentication? | Yes |
| Requires SSL? | Yes |
| Query Parameters: | |
| test | The test flag (eg 1 or 0, optional) |
| user | Your Registrar ID (eg H12345) |
| password | Your Toolkit Password |
| handle | The ID of the contact object to be modified |
| name | The new name for the contact object (optional) |
| company | The new company/organisation for the contact object (optional) |
| street1 | The new street address for the contact object (optional) |
| street2 | The new street address for the contact object (optional) |
| street3 | The new street address for the contact object (optional) |
| city | The new city for the contact object (optional) |
| sp | The new state/province for the contact object (optional) |
| postcode | The new postcode for the contact object (optional) |
| country | The new country for the contact object (optional) |
| phone | The new phone number for the contact object (optional) |
| fax | The new fax number for the contact object (optional) |
| The new email for the contact object (optional) | |
| visible | Whether to show the contact object in WHOIS records (1 or 0, optional) |
This function allows you to update the contact details of any contact object for which you are the "sponsor". You will be the "sponsor" for any contact object that is created through the create_handle, register or modify functions. You will also probably be the sponsor for any contact object that is the registrant for a domain on your account (the exception is when that contact object is also associated with domain names on another registrar's account, in that situation neither registrar has sponsorship).
Please note that this function must not be used merely to change the registrant for a domain name to an entirely new entity (as contacts may be associated with multiple domain names), but only for incremental corrections to contact details.
NB: You do not need to specify all the contact details if you only wish to change a subset of them.
- handle must be the unique ID assigned to each contact object.
- name, company, street1, street2, street3, city, sp and postcode must all be plain text strings.
- country must be a two-character ISO-3166 country code, (UK is allowed in place of GB).
-
phone and fax should be formatted in an e164a-compliant format, eg:
+44.8700170900
- email must be a valid e-mail address.
- visible is a binary value that controls whether the contact object's contact details are show in WHOIS records for domain names to which it is associated. A value of 0 makes the contact object "invisible".
Legacy Parameters
Prior to September 2006 this function accepted an address parameter for old-style flat address data. While this parameter is still supported, its use is not recommended in new client code.
Response Format
Responses from the server will have the form
Transaction-ID: e2ca01ad7135e787a5e97ad5b421ed74 Status: 0 Message: Handle modified OK
In the event of an error, the server will return a response of the form
Transaction-ID: e2ca01ad7135e787a5e97ad5b421ed74 Status: 1 Message: Permission denied.