Ergani II Docs

Core workflows

Submit a WRKCardSE event when an employee arrives, marking the start of a work shift.

Submit a WRKCardSE event when an employee leaves, marking the end of a work shift.

Obtain and refresh the access token required for every Web API request.

Resubmit a check-in or check-out for the same employee and date — the most recent submission wins.

Authenticate — POST your credentials to get an access token.
Send a WRKCardSE request — POST a check-in or check-out event for an employee.
Receive a protocol number — A successful submission returns a protocol number — your proof of receipt.
Done — The event is recorded in Ergani. No further action needed.

Send WRKCardSE check-in and check-out events for employees in real time.

Each event becomes part of an employee's attendance record in Ergani.

Submissions satisfy the employer's Digital Work Card reporting obligations under Greek labour law.

No server-side idempotency guarantee — submitting the same event twice creates two records.
Most recent submission wins — a later check-in/check-out for the same employee and date overrides the earlier one.
Strict timestamp rules — events must reflect the actual time of arrival/departure; late submissions require justification codes.
Client must handle retries and failures — the API does not retry on your behalf, and a failed request may or may not have been recorded.

See the production guide and error reference for how to handle these in practice.