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
AuthorizationstringRequired

Please enter a valid token

Query parameters
idinteger · int32Optional
uidstring · uuidOptional
Bodyobject[]
customerIdstring | nullableOptional
classificationstring | nullableOptional
dwhIdstring | nullableOptional
beacinteger · int32 | nullableOptional
egidstring | nullableOptional
edidstring | nullableOptional
postAddressIdstring | 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
freetext1string | nullableOptional
freetext2string | nullableOptional
freetext3string | nullableOptional
freetext4string | nullableOptional
freetext5string | nullableOptional
Responses
200

OK

No content
put
/AddressProcessing/AddRecords
PUT /v2/AddressProcessing/AddRecords HTTP/1.1
Host: api.multisource.ch
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 509

[
  {
    "customerId": "text",
    "classification": "text",
    "dwhId": "text",
    "beac": 1,
    "egid": "text",
    "edid": "text",
    "postAddressId": "text",
    "firstname": "text",
    "companyName": "text",
    "name": "text",
    "birthDate": "text",
    "street": "text",
    "streetNo": "text",
    "streetAdd": "text",
    "careOf": "text",
    "poBox": "text",
    "poZip": "text",
    "poTown": "text",
    "zip": "text",
    "town": "text",
    "mobileNo": "text",
    "phoneNo": "text",
    "email": "text",
    "uid": "text",
    "chnr": "text",
    "freetext1": "text",
    "freetext2": "text",
    "freetext3": "text",
    "freetext4": "text",
    "freetext5": "text"
  }
]
200

OK

No content

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.

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
AuthorizationstringRequired

Please enter a valid token

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

OK

No content
post
/AddressProcessing/FileUpload
POST /v2/AddressProcessing/FileUpload HTTP/1.1
Host: api.multisource.ch
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: multipart/form-data
Accept: */*
Content-Length: 17

{
  "file": "binary"
}
200

OK

No content
PreviousDataNextData Output

Last updated