Skip to content
Chronikum

abas ERP and the battery passport: integration pattern

How data from abas ERP (abas Software (Forterro)) 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
abas Software (Forterro)
Deployments
On-premise (abas ERP); Cloud (abas ERP (hosted))
Checked
community source only, 24 October 2026
Managed integration
—

From vendor marketing only: a REST API and abas Connect are named; there was no public developer documentation.

Interfaces

InterfaceProtocolSign-inEventsObjectsChecked
REST APIREST APIRESTTokennoneProduct/material master, Batch/serial numbercommunity or marketing source only, 24/10/2026

Matching workflows

Import presets

Guide in the developer documentation (after sign-in)

← All integration patterns