EORI Validation: JSON import interface

With the import interface for JSON files, the module “EORI Validation” offers you a possibility to check your entire data set from your master data.

We make sure that compatibility is always maintained when extending the JSON EORI interface. This means that you can always use the latest version without generating additional effort when integrating it into your ERP system.

In order to be able to uniquely assign a JSON data record from your ERP system in the EORI Validation, you have the option of specifying up to two unique keys in the import file. These will be returned in the export file and can be used for re-import into your ERP system. However, you can also leave these two fields (key1 and key2) blank. They are not necessary for processing.

Since the EORI interface also returns the name and address, in a future release of the EORI Validation we will also enable a check of your stored data and extend the JSON interface.

Please note that all bold fields must be specified in the import file.

Structure — EORI JSON Import File

Key Format Example
key1 String 4711
key2 String 2
eori String EN123456

Example in the form of a JSON file with two entries:

[
{
"key1": "a",
"key2": "b",
"eori": "EN123456"
},
{
"key1": "a",
"key2": "b",
"eori": "EN789012"
}
]

Structure — EORI JSON Export File

The EORI check JSON export file contains the returned values of each check, also in the same data format unless otherwise specified. Please note that the JSON interface outputs all available fields and thus represents the most complete format.

Key Format Example
key1 String 4711
key2 String 2
eori String DE123456
name String Sample Company
address String
street String Samplestreet 1
postalCode String 12345
city String Village of Samples
country String Germany
status String 0
statusDescr String Valid
errorReason String
requestdate String

Example in the form of a JSON file (with standard delimiter):

[
{
"eori": "EN123456";
"status": "0",
"StatusDescr": "Valid",
'name' means 'sample company';
"street": "Sample Street 1",
"PostalCode": "12345",
"city": "Musterdorf",
"country": "Germany",
"requestdate": "30/01/2021",
"key1": "4711",
"key2": "2"
}
]

In contrast to XLSX or CSV, we have agreed on the pure English notation of the keys of the EORI Validation within JSON. This allows us to avoid runtime errors in case of an incorrect conversion from the beginning.

Please note that the fields in the export file of the EORI Validation are not always output in the same order as specified in the table above.