# Chemilla Labels integration examples

Start without a real ERP or printer:

```bash
npx -p @chemilla/labels-mcp labels-sandbox
```

The local sandbox listens on `127.0.0.1:5055`, accepts a dummy bearer token, validates the public payload contract, and returns deterministic fake job IDs. It never contacts Chemilla Labels or physical hardware.

Available references:

- [TypeScript / Node.js](./typescript.mjs) — executable client for validation and enqueue.
- [C# / .NET](./csharp.cs) — executable-style reference using `HttpClient`.
- [Business Central AL](./business-central.al) — reference codeunit using `HttpClient`; adapt and test in the customer's extension and BC version.
- [SAP ABAP](./sap-abap.abap) — reference HTTP client; adapt authentication, secure storage, and event wiring in the customer's SAP landscape.
- [Example payload](./print-job.json) — same contract for every source system.
- [Postman collection](./postman-collection.json) — token, validation, and enqueue requests.

Business Central and SAP files are not preinstalled or certified connectors. The supported boundary is the [Print API](https://labels.f1cs-dev.it/v2/openapi.yaml).
