---
title: "Email Parser guide"
url: "https://help.internetx.com/en/api/additional-email-parser-guide/"
lang: "en"
section: "API reference — Additional API functions"
updated: "2023-09-27"
---

# Email Parser guide

The Email Parser guide helps you to parse ideal answers from our API.

Recommandation

For automated processing, we recommend using the XML email format. You can do this in the _UserProfile/API Settings._

## Introduction

An unmistakable order identifier must be generated in your own system and transferred to the XML interface as ctid. The order number is marked as transaction in the email response. The important sections of the email response are `**highlighted red**`. These must be parsed to process the response.

An email consists of these blocks:

|  |  |
| --- | --- |
| system | always |
| reply | empty for “away”- messages |
| nic\_response | optional |

Details like status and transaction ID are listed in the section system.The details of the order are listed in the section reply. 

The section nic response lists the detailed response from the registry, in which a detailed error message may also be included. 

Generally, the status from the section system should be parsed, in order to decide which further details are needed to classify the order. 

The following emails must be parsed: 

## Emails to be parsed

### DomainAway/AutoACK

AutoDNS confirmed an ongoing transfer with an ACK. (Only for gTLDs due to the IRTP Policy, normally there is a NACK). 

| <system><br>user: ExampleUser<br>task: 1403008<br>status: S1403008 \[The request was not answered in time. AUTO-ACK<br>was processed.\]<br>success\_value: domain: [example.org](http://example.org)<br>last\_transaction: 124124124<br>kk\_answer: AUTOACK<br></system><br><reply><br>kk\_new: 500123<br>kk\_start: 2010-05-11 19:43:02<br>kk\_reminder: 2010-05-14 19:43:02<br>kk\_autoack: 2010-05-16 19:43:02<br>kk\_end: 2010-05-16 19:43:02<br></reply> |
| --- |

Status S1403008 indicates that the domain name which was transferred away can be found with the keyword _success\_value_.  
Or an outgoing transfer has been confirmed by the NIC and the domain has been removed. E.g. from .AT or .EU.

| <system><br>user: ExampleUser<br>task: 0106<br>status: S0106 \[Outgoing domain transfer has been answered<br>successfully.\]<br>notice: MSG010409 \[The registry removed the domain from your<br>inventory. You are no longer the OwnerC of the domain.\]<br>kk\_answer: ACK<br></system><br><reply><br>sld: example<br>tld: at<br></reply> |
| --- |

In this case, the status indicates that the domain name that was transferred out is listed in the _reply_ block. You must then remove it from your own system.  
The registrar cannot interfere with this transfer – the domain owner can transfer out the domain without registrar approval.

#### Transfer AutoNACK

| <system><br>user: ExampleUser<br>task: 1403005<br>status: S1403005 \[The request was not answered in time. AUTO-NACK<br>was processed.\]<br>success\_value: domain: [example.net](http://example.net)<br>transaction: 1273833236<br>kk\_answer: NACK<br></system> |
| --- |

#### Transfer Reminder

This notification is sent when an outgoing transfer has already been ongoing for a while. It serves as a reminder and can be used for monitoring, i.e. as a trigger for AUTONACKs.

| <system><br>user: ExampleUser<br>task: 1403006<br>status: S1403006 \[Reminder! Outgoing transfer was started.\]<br>success\_value: domain: [example.com](http://example.com)<br>transaction: 1273952471<br></system> |
| --- |

#### Transfer Out Notification

The domain transfer has been started by another registrar.

| <system><br>user: ExampleUser<br>task: 1403<br>status: S1403 \[Outgoing domain transfer has been started<br>successfully.\]<br>success\_value: domain: [example.com](http://example.com)<br>transaction: 1234<br></system><br><reply><br>kk\_new: 99<br>kk\_start: 2010-05-17 08:43:53<br>kk\_reminder: 2010-05-20 08:43:53<br>kk\_autonack: 2010-05-22 02:43:53<br>kk\_end: 2010-05-22 08:43:53<br></reply> |
| --- |

Status S1403 indicates that the domain name can be found with _success\_value_. This domain will be transferred out. A reply with ACK/NACK is possible.

#### Confirmation Emails for Domain Orders

##### Domain Create

Success

| <system><br>user: ExampleUser<br>task: 0101<br>status: S0101 \[Domain has been registered successfully.\]<br>transaction: bf296d8dffc4<br>last\_transaction: bf296d8dffc4<br></system> |
| --- |

Failed

| <system><br>user: ExampleUser<br>task: 0101<br>status: E0101 \[Domain could not be registered.\]<br>transaction: 201005061621<br></system> |
| --- |

Status S0101 and E0101 indicate that the order number can be found in the transaction field.

##### Domain Update

Success

| <system><br>user: ExampleUser<br>task: 0102<br>status: S0102 \[Domain has been updated successfully.\]<br>transaction: 4bed8920b56fb<br>last\_transaction: 4bed8920b56fb<br></system> |
| --- |

Failed

| <system><br>user: ExampleUser<br>task: 0102<br>status: E0102 \[Domain could not be updated\]<br>error: 533001291da2<br>transaction: bed7c6845726<br></system> |
| --- |

Status S0102 and E0102 indicate that the order number can be found in the transaction field. The update can be ignored if it happens without or with an unknown transaction ID.

Success with Deletion of the AuthInfo

| <system><br>user: ExampleUser<br>task: 0102<br>status: S0102 \[The domain has been updated successfully\]<br>notice: MSG011304 \[The existing AuthInfo was deleted by the<br>request.\]<br>transaction: qs1282921089<br>last\_transaction: qs1282921089<br></system> |
| --- |

#### Domain Delete

Success

| <system><br>user: ExampleUser<br>task: 0103<br>status: S0103 \[Domain has been deleted successfully.\]<br>transaction: 29a489dadaf0<br></system> |
| --- |

Failed

| <system><br>user: ExampleUser<br>task: 0104<br>status: S0104 \[Domain transfer has been started successfully.\]<br>transaction: q1273s146x50<br></system> |
| --- |

Status S0103 and E0103 indicate that the order number can be found in the transaction field.

#### Domain Update (AutoUpdate)

After a transfer, an AUTOUPDATE will be started. The transaction id is the same as with domain transfer. The AUTOUPDATE will update, if necessary, name servers and other contacts.  
Analogue parsing will follow after a domain update as above. If the AUTOUPDATE failed, the error messages will help you to see which problem had occurred.

| <system><br>user: ExampleUser<br>task: 0102<br>status: S0102 \[Domain has been updated successfully.\]<br>transaction: q1273s146x50<br>last\_transaction: q1273s146x50<br>autoupdate: true<br></system> |
| --- |

If the OwnerC is imported during this step, the following notification is shown:

| <system><br>user: ExampleUser<br>task: 0102<br>status: S0102 \[Domain has been updated successfully.\]<br>notice: MSG01050 \[Ownerc has been imported\]<br>transaction: q1273s146x50<br>last\_transaction: q1273s146x50<br>autoupdate: true<br></system> |
| --- |

In this case, the message should not be ignored. You can readout the domain contact ID of the new OwnerC in the “reply” block:

| <reply><br>tld: es<br>sld: test<br>owner: ExampleUser<br>owner\_context: 4<br>owner-c: 12345<br>\[...\]<br></reply> |
| --- |

#### Domain Transfer ACK with OwnerC Import

Depending on the TLD, the OwnerC can also be imported directly with the ACK.

| <system><br>user: ExampleUser<br>task: 0104001<br>status: S0104001 \[The incoming domain transfer (ACK) has been<br>completed successfully.\]<br>transaction: q1273s146x50<br>notice: MSG01050 \[OwnerC has been imported\]<br></system> |
| --- |

#### Domain Transfer ACK

| <system><br>user: ExampleUser<br>task: 0104001<br>status: S0104001 \[The incoming domain transfer (ACK) has been<br>completed successfully.\]<br>transaction: q1273s146x50<br>last\_transaction: id #20673# action #domain#<br></system> |
| --- |

#### Domain Transfer NACK

| <system><br>user: ExampleUser<br>task: 0104001<br>status: E0104001 \[Incoming domain transfer (NACK) could not be<br>completed successfully.\]<br>error: 63370088701<br>transaction: e3ec9bc8ec70<br></system> |
| --- |

This NACK comes with the Status E0104001.