After processing your operation the Automaton will automatically respond with an email. The response you receive will vary on two factors: the operation you submitted and whether your operation was successful.

These are the possible responses from the Automaton:

• Create confirmation
• Delete confirmation
• Fatal error
• Fork confirmation
• List response
• List-all response
• Lock domain response
• Lock account response
• Merge confirmation
• Modify domain confirmation
• Modify account confirmation
• Modify contact confirmation
• Modify nameserver confirmation
• Non-fatal error
• Query domain response
• Query account response
• Query contact response
• Query nameserver response
• Receive accept confirmation
• Receive reject confirmation
• Release confirmation
• Release with handshake confirmation
• Renew confirmation
• Unlock domain confirmation
• Unlock account confirmation
• Unrenew confirmation

---

Notes

1. The domain name automaton-example.co.uk is an example and will be replaced by the domain name you registered.
2. The account-id S10001 is an example.  It will be replaced with the account-id of an account object if one was created as part of your registration.
3. The adminsitrative contact names Collin J. West, Connie B. Elliott and Lucas C. Smith plus their coresponding contact-ids C10002, C10003 and C10004 are examples.  These will be replaced with the name and contact-id of any contact objects that were created as part of your registration.
4. The number of contacts and nameservers objects listed in the response will vary depending on the number of objects that were created as part of your registration.

Notes

1. The TAG in the subject line will be replaced by your TAG.
2. The domain name automaton-example.co.uk is an example and will be replaced by the domain name you deleted.

Notes

1. [Received_subject] is replaced with the subject of the original operation.
2. [Error_code Error_message] is one of the fatal error codes.
3. [Original_message] is a complete copy of the message that caused the error.

1. The TAG in the subject line will be replaced by your TAG.

Notes:

1. There are no line breaks in the data fields in the actual reply.  These are only shown here for illustrative purposes.  In the actual message the data for each domain is on one line.  There is one line of data for each domain.
2. All dates are in the format YYYYMMDD.
3. [Number] is replaced with the correct number for the number of domains returned.
4. All new line characters are replaced with '^'.
5. The maximum outgoing message size the Automaton can send is limited to 250MB.  This equates to a list message of approximately 500,000 domains.
6. The registrar-tag field will be ips-key and account-name registrant if you have the backwards compatibility option switched on.

Notes:

1. There are no line breaks in the data fields in the actual reply.  These are only shown here for illustrative purposes.  In the actual message the data for each domain is on one line.  There is one line of data for each domain.
2. All dates are in the format YYYYMMDD.
3. [Number] is replaced with the correct number for the number of domains returned.
4. All new line characters are replaced with '^'.
5. The maximum outgoing message size the Automaton can send is limited to 250MB.  This equates to a list message of approximately 500,000 domains.
6. The registrar-tag field will be ips-key and account-name registrant if you have the backwards compatibility option switched on.

Notes

1. The TAG in the subject line will be replaced by your TAG.
2. The domain name automaton-example.co.uk is an example and will be replaced by the domain name you locked.

Notes

1. The TAG in the subject line will be replaced by your TAG.
2. The account-id 100236 is an example and will be replaced by account you locked.
3. The type may be 'investigation' or 'opt-out' depending upon the lock type requested.

Notes

1. The TAG in the subject line will be replaced by your TAG.

Notes

1. The TAG in the subject line will be replaced by your TAG.
2. The identifier creation section appears only when new contacts are added.

Notes

1. The TAG in the subject line will be replaced by your TAG.
2. The identifier creation section appears only when new nameservers or contacts are added.

Notes

1. The TAG in the subject line will be replaced by your TAG.

Notes

1. The TAG in the subject line will be replaced by your TAG.

Notes

1. If a non-fatal error occurs then a section will be appended to the reply template below explaining what these errors were.

Notes

1. TAG in the subject line is replaced with your tag.
2. Blank fields are not included, they are all shown here for illustrative purposes.
3. Different field names may be returned if backwards compatibility is enabled in your registry options, depricated field names can be found on our field definitions page.
4. DNS entries are not stored in a particular order.

Notes

1. TAG in the subject line is replaced with your tag.
2. Blank fields are not included, they are all shown here for illustrative purposes.
3. Different field names may be returned if backwards compatibility is enabled in your registry options, depricated field names can be found on our field definitions page.

Notes

1. TAG in the subject line is replaced with your tag.
2. Blank fields are not included, they are all shown here for illustrative purposes.

Notes

1. TAG in the subject line is replaced with your tag.
2. Blank fields are not included, they are all shown here for illustrative purposes.

Notes

1. TAG in the subject line is replaced with your tag.

Notes

1. TAG in the subject line is replaced with your tag.

Notes

1. TAG in the subject line is replaced with your tag.

Notes

1. TAG in the subject line is replaced with your tag.

Notes

1. TAG in the subject line is replaced with your tag.

Notes

1. TAG in the subject line is replaced with your tag.

Notes

1. TAG in the subject line is replaced with your tag.
2. The type may be 'investigation' or 'opt-out'.

Notes

1. TAG in the subject line is replaced with your tag.