Skip to content
Chronikum

weclapp and the battery passport: integration pattern

How data from weclapp (weclapp) reaches the battery passport through the Chronikum API: interfaces, workflows and when we checked them.

An integration pattern, not a ready-made connector: your ERP or integration platform reads and writes through the Chronikum API with an organisation key. The details below come from the vendor documentation and were checked on the date given.

Vendor
weclapp
Deployments
Cloud (weclapp (REST API v1))
Checked
vendor documentation, 24 October 2026
Managed integration
—

The API token goes in the AuthenticationToken header; it belongs to a user, so create a technical user with narrow rights.

Interfaces

InterfaceProtocolSign-inEventsObjectsChecked
REST APIArticles, serial numbers, shipmentsRESTAPI keynoneProduct/material master, Batch/serial number, Delivery/goods issuechecked in the vendor documentation, 24/10/2026

Matching workflows

Import presets

Guide in the developer documentation (after sign-in)

← All integration patterns