JSON import interface

available from ID Validation 1.5.0 / free for all existing customers

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

We make sure that compatibility is always maintained when extending the JSON duplicate 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 duplicate check, you have the option, specify 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 the not necessary.

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

Structure - import file

fieldformatexample
key1String
key2String
firstnameString
lastnameString
name1String
name2String
name3String
name4String
streetString
numberString
postcodeString
townString
departmentString
countryString

Example in the form of a JSON file:

[
    {
        "key1":"val_key1",
        "key2":"val_key2",
        "firstname":"val_firstname",
        "lastname":"val_lastname",
        "name1":"val_name1",
        "name2":"val_name2",
        "name3":"val_name3",
        "name4":"val_name4",
        "street":"val_street",
        "number":"val_number",
        "postcode":"val_postcode",
        "town":"val_town",
        "department":"val_department",
        "country":"val_country"
    },
    {...}
]

Structure - export file

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

fieldformatexample
internalidString
key1String
key2String
firstnameString
lastnameString
name1String
name2String
name3String
name4String
streetString
numberString
postcodeString
townString
departmentString
countryString
// cleaned data
cleaned firstnameString
cleaned lastnameString
cleaned name1String
cleaned name2String
cleaned name3String
cleaned name4String
cleaned streetString
cleaned numberString
cleaned postcodeString
cleaned townString
cleaned departmentString
cleaned countryString
// applied cleaners
applied cleanersString
// applied duplicates
duplicate idsString
address groupString

In contrast to XLSX or CSV, we have agreed on the pure English notation of the duplicate check keys within JSON. This allows us to avoid runtime avoid runtime errors in case of a faulty conversion.