Skip to content
BatteryPass

Epicor Kinetic and the battery passport: integration pattern

How data from Epicor Kinetic (Epicor) reaches the battery passport through the BatteryPass 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 BatteryPass API with an organisation key. The details below come from the vendor documentation and were checked on the date given.

Vendor
Epicor
Deployments
Cloud (Epicor Kinetic (REST API v2)); On-premise (Epicor Kinetic (REST API v2))
Checked
community source only, 24 October 2026
Managed integration
—

From community sources only: REST API v2 needs an API key in the x-api-key header in addition to the user sign-in. Never send the key as a query parameter.

Interfaces

InterfaceProtocolSign-inEventsObjectsChecked
REST API v2Business objects over RESTRESTAPI key, Basic authnoneProduct/material master, Batch/serial number, Production order, Delivery/goods issuecommunity or marketing source only, 24/10/2026

Matching workflows

Import presets

Guide in the developer documentation (after sign-in)

← All integration patterns