Terminal-Stempelung
Flat body (ADR 0005, frozen hardware contract — TerminalResponsePinTest): the EventResource fields plus the top-level `terminal_message`. Documented explicitly because the shape is assembled from a resolved resource, which leaves nothing inferrable for the schema generator.
Bearer-Token, erhalten über den Login-Endpunkt (POST /rest/login).
Ort: header
Pfadparameter
Response-Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/terminal/string"{ "id": "string", "employee_id": "string", "state": 0, "type": 0, "timestamp": "string", "latitude": "string", "longitude": "string", "accuracy": 0, "nfc_tag_id": "string", "client_ip": "string", "metadata": { "property1": null, "property2": null }, "early": 0, "created_at": "string", "updated_at": "string", "terminal_message": "string"}Einrichtungscode einlösen POST
Returns the same payload as `POST /rest/login`. Every failure mode (unknown, expired, revoked, already redeemed, blocked account) answers with the identical 422 so token state cannot be probed.
Mobile Stempelung POST
Documented exception to the `data`-envelope standard (ADR 0005): the payload stays flat for the mobile clients. `early` is only present when the clock-in happened before the rostered start (milliseconds early).