Data Input

The multisource•api can process incoming data in two ways – either directly via the API (AddRecords) or through a file upload.

AddRecords (API-based input)

Mapping and data import can be performed directly through the API.

put
/addressprocessing/AddRecords
Authorizations
auth-keystringRequired

API Key required for authorized endpoints

Query parameters
idinteger · int32Optional
uidstring · uuidOptional
Bodyobject[]
customerIdstring · nullableOptional
classificationstring · nullableOptional
dwhIdstring · nullableOptional
kbbCompanyIdinteger · int32 · nullableOptional
kbcPersonIdinteger · int32 · nullableOptional
kbcHouseholdIdinteger · int32 · nullableOptional
beacinteger · int32 · nullableOptional
egidstring · nullableOptional
edidstring · nullableOptional
postAddressIdstring · nullableOptional
freetext1string · nullableOptional
freetext2string · nullableOptional
freetext3string · nullableOptional
freetext4string · nullableOptional
freetext5string · nullableOptional
firstnamestring · nullableOptional
companyNamestring · nullableOptional
namestring · nullableOptional
birthDatestring · nullableOptional
streetstring · nullableOptional
streetNostring · nullableOptional
streetAddstring · nullableOptional
careOfstring · nullableOptional
poBoxstring · nullableOptional
poZipstring · nullableOptional
poTownstring · nullableOptional
zipstring · nullableOptional
townstring · nullableOptional
mobileNostring · nullableOptional
phoneNostring · nullableOptional
emailstring · nullableOptional
uidstring · nullableOptional
chnrstring · nullableOptional
Responses
chevron-right
200

OK

stringOptional
put
/addressprocessing/AddRecords
200

OK

File upload

Customer data can be uploaded in any structured format such as TXT, CSV, TSV, or XLSX.

Two mapping options are available:

Standard mapping

The multisource•api provides a preconfigured standard mapping that covers the most common field names (name, first name, street, house number, postal code, city, etc.).

Custom mapping

Alternatively, a customer-specific mapping can be defined. This is created jointly during the onboarding process.

Multiple mappings can also be defined in parallel – for example, when data originates from different source systems with varying field structures.

circle-info

The API can generally handle almost any structured data format.

For optimal matching, it is recommended to fill in at least the following fields: name, first name, street, house number, postal code, and city.

post
/addressprocessing/FileUpload
Authorizations
auth-keystringRequired

API Key required for authorized endpoints

Query parameters
batchIdinteger · int32Optional
batchUidstring · uuidOptional
descriptionstringOptional
Body
filestring · binaryOptional
Responses
chevron-right
200

OK

stringOptional
post
/addressprocessing/FileUpload
200

OK

Last updated