# Epicor Kinetic

> How Epicor Kinetic could supply serial numbers to BatteryPass through REST API v2.

> [!WARNING]
> The facts on this page come from community sources only and are not checked against Epicor documentation. Confirm the
> interfaces and sign-in with Epicor or your partner before a project.

> [!NOTE]
> This page describes an integration pattern. BatteryPass ships no connector for Epicor Kinetic and has no partnership
> with Epicor; nothing here is a vendor approval.

According to community sources, REST API v2 of Kinetic exposes the business objects over REST and needs an API key in
the `x-api-key` header in addition to the user sign-in. Never send that key as a query parameter: URLs end up in logs.
Use a technical user with read rights only, and keep both secrets in a vault.

A middleware reads the serial numbers of finished jobs and writes a file with the `generic-csv` preset for
[units from production](https://passport.kabin.sh/docs/en/integrations/workflows/units-from-production). Change events were not checked; poll
on a schedule until they are.

## Interfaces and how they were checked

- **Vendor:** Epicor
- **Cloud:** Epicor Kinetic (REST API v2)
- **On-premise:** Epicor Kinetic (REST API v2)

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.

An integration pattern, not a connector: BatteryPass ships no ERP connector and holds no vendor certification.

| Interface                                                                                                             | Protocol | Sign-in             | Events | Objects                                                                              | Checked                                        |
| --------------------------------------------------------------------------------------------------------------------- | -------- | ------------------- | ------ | ------------------------------------------------------------------------------------ | ---------------------------------------------- |
| [`REST API v2`](https://www.epiusers.help/t/rest-interface-header-key-value-pairs/44309) (Business objects over REST) | REST     | API key, Basic auth | none   | Product/material master, Batch/serial number, Production order, Delivery/goods issue | community or marketing source only, 24/10/2026 |

**Import presets: Generic CSV file** (`generic-csv`): For any ERP and for files a middleware writes itself: GTIN, serial number, manufacturing date, facility (name or GLN), model version and battery status, with German and English column names.

| Column in the export                                          | Field in BatteryPass                                      |
| ------------------------------------------------------------- | --------------------------------------------------------- |
| `GTIN` (also EAN, GTIN-13, GTIN-14)                           | GTIN (GS1) `identification.gtin`                          |
| `Serial number` (also Seriennummer, serial_number)            | Serial number `identification.serial_number`              |
| `Manufacturing date` (also Herstelldatum, manufacturing_date) | Manufacturing date `identification.manufacturing_date`    |
| `Facility` (also Produktionsstätte, Facility GLN, Werk-GLN)   | Place of manufacture `identification.manufacturing_place` |
| `Model version` (also Modellversion, model_version)           | Model version `model_version`                             |
| `Battery status` (also Batteriestatus, battery_status)        | Battery status `identification.battery_status`            |

## Workflows

- [Units from production](https://passport.kabin.sh/docs/en/integrations/workflows/units-from-production.md): Serial numbers from the production confirmation or goods receipt are staged as an import; members review, commit and approve before any passport appears. Key scopes: import
- [Passport links back into the ERP](https://passport.kabin.sh/docs/en/integrations/workflows/passport-links-to-erp.md): The middleware follows the change feed and writes the GS1 Digital Link and the passport status to the serial number record in the ERP, so labels and delivery papers carry it. Key scopes: read
- [Returns and repairs as lifecycle events](https://passport.kabin.sh/docs/en/integrations/workflows/returns-and-repairs.md): Completed repairs, inspections and component replacements from service or return orders appear as events in the unit's history. Key scopes: read, condition
- [Product change leads to a new model version](https://passport.kabin.sh/docs/en/integrations/workflows/product-change.md): A change to the product master in the ERP triggers a notification; a member creates a new model version in BatteryPass. Declared data is never written automatically. Key scopes: read