# Production Records

Endpoints for creating and managing production records

## Create a production record

 - [POST /api/control/production/records](https://docs.hydrobit.ag/spec/openapi/production-records/createproductionrecord.md): Creates a new production record to add units to an open session.

Requires JWT token authentication in the Authorization header.

Key features:
- Only the session owner can create records
- Session must be open
- Supports idempotency via clientEventId and optional idempotencyKey
- Optimized for high-performance processing

## Bulk create production records

 - [POST /api/control/production/records/bulk](https://docs.hydrobit.ag/spec/openapi/production-records/bulkcreateproductionrecords.md): Creates multiple production records in a single request (offline sync).

Requires JWT token authentication in the Authorization header.

Each record is processed independently with full validation and idempotency.
Returns multi-status response (207) with individual results.

## Check idempotency key

 - [HEAD /api/control/production/records/check-idempotency](https://docs.hydrobit.ag/spec/openapi/production-records/checkidempotencykey.md): Checks if an idempotency key has been used before.

Requires JWT token authentication in the Authorization header.

Returns 200 if key exists, 404 if not.

## Get a production record

 - [GET /api/control/production/records/{recordId}](https://docs.hydrobit.ag/spec/openapi/production-records/getproductionrecord.md): Retrieves detailed information about a specific production record.

Requires JWT token authentication in the Authorization header.

## Void a production record

 - [POST /api/control/production/records/{recordId}/void](https://docs.hydrobit.ag/spec/openapi/production-records/voidproductionrecord.md): Voids (cancels) a production record by creating a counter-movement with negative units.

Requires JWT token authentication in the Authorization header.

Only the session owner can void records. Session must be open.
Supports idempotency - voiding the same record multiple times is safe.