# weclapp

> How weclapp hands articles and serial numbers to BatteryPass through its REST API.

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

The REST API of weclapp takes the API token in the `AuthenticationToken` header. The token belongs to a user, so create
a technical user with narrow rights for the integration and keep its token in a vault next to the BatteryPass key.

The middleware reads articles and serial numbers of finished production, writes a file with the `generic-csv` preset and
stages it as in [units from production](https://passport.kabin.sh/docs/en/integrations/workflows/units-from-production). Webhooks were not
checked; poll on a schedule unless you confirm them. Passport links can go back to the article or serial number record as
in [passport links back into the ERP](https://passport.kabin.sh/docs/en/integrations/workflows/passport-links-to-erp).

## Interfaces and how they were checked

- **Vendor:** weclapp
- **Cloud:** weclapp (REST API v1)

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

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`](https://www.weclapp.com/api/) (Articles, serial numbers, shipments) | REST     | API key | none   | Product/material master, Batch/serial number, Delivery/goods issue | checked in the vendor documentation, 24/10/2026 |

**Notes**

- `REST API`: Webhooks not checked.

**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