Environments & Companion Files
Trial vs. Production environments
| Trial (Δοκιμαστικό) | Production (Παραγωγικό) | |
|---|---|---|
| Portal | https://trialv2eservices.yeka.gr | https://eservices.yeka.gr |
| REST API | https://trialv2eservices.yeka.gr/WebservicesAPI/Api/ | https://eservices.yeka.gr/WebservicesAPI/Api/ |
| API UI | https://trialv2eservices.yeka.gr/WebservicesAPIUI/ | https://eservices.yeka.gr/WebservicesAPIUI/ |
| Login | e-ΕΦΚΑ credentials; branch users can be created for testing | e-ΕΦΚΑ credentials for the production environment |
| Legal effect | None — submissions are marked "ΑΚΥΡΟ" (void) | Legally binding |
The corresponding XSD schemas and companion files are available on the
trial environment's landing page, in a downloadable ZIP archive
(HELP_FILES_SAMPLES.zip), which also contains a Postman collection
(ERGANI.postman_collection.json).
Companion files by declaration type
| Declaration | Action | File type | Filename | API submission code |
|---|---|---|---|---|
| Employment Relationship Change | XML upload | XSD | WorkingStatusChange_v1.xsd | — |
| Employment Relationship Change | XML upload | XML example | WorkingStatusChanges.xml | — |
| Employment Relationship Change | Web API (JSON) | JSON example | WorkingStatusChanges.json | WKChgWK |
| Fixed Weekly Schedule | Excel bulk upload | XLSX example | EXCEL_PROTOTYPE_WEEKLY.xlsx | — |
| Fixed Weekly Schedule | XML upload | XSD | WTO_Weekly_v1.xsd | — |
| Fixed Weekly Schedule | XML upload | XML example | WTOWEEKLY.xml | — |
| Fixed Weekly Schedule | Web API (JSON) | JSON example | WTOWEEKLY.json | WTOWeek |
| Variable/Modified Per-Day | Excel bulk upload | XLSX example | EXCEL_PROTOTYPE_DAILY_PROGRAM.xlsx | — |
| Variable/Modified Per-Day | XML upload | XSD | WTO_v1.xsd | — |
| Variable/Modified Per-Day | XML upload | XML example | WTODAILY.xml | — |
| Variable/Modified Per-Day | Web API (JSON) | JSON example | WTODaily.json | WTODaily |
| Leaves | Excel bulk upload | XLSX example | EXCEL_PROTOTYPE_DAILY_LEAVES.xlsx | — |
| Leaves | XML upload | XSD | WTO_v2.xsd | — |
| Leaves | XML upload | XML examples | wtoHoliday_v2.xml, wtoHolidayCor_v2.xml | — |
| Leaves | Web API (JSON) | JSON examples | wtoHoliday_v2.json, wtoHolidayCor_v2.json | — |
| Overtime (E8) | XML upload | XSD | EOvertime_v2.xsd | — |
| Overtime (E8) | XML upload | XML example | Overtime.xml | — |
| Overtime (E8) | Web API (JSON) | JSON example | Overtime.json | OvTime |
| Hiring (E3) | XML upload | XSD | E3_v6.xsd | — |
| Hiring (E3) | XML upload | XML example | E3.xml | — |
| Hiring (E3) | Web API (JSON) | JSON example | E3.json | E3 |
| Variable/Modified Per-Day (Απολογιστικό) | XML upload | XSD | WTO_v1.xsd | WTODailyA |
| Overtime (E8 Απολογιστικό) | XML upload | XSD | EOvertime_v2.xsd | OvTimeA |
| 6th-Day Employment Declaration | XML upload | XSD | SixthDay_v1.xsd | SixthDay |
| Exemption from Pre-Announcement | XML upload | XSD | ExProan.xsd | ExProan |
Mass termination of active overtime (E8 Μαζική Λήξη)
For employers with many currently active (τρέχουσες) legal overtime
declarations (E8 / OvTime), the ΠΣ ΕΡΓΑΝΗ portal provides a bulk-termination
workflow:
ΕΝΤΥΠΑ ΣΕΠΕ → Υπερωρίες → Μαζική Λήξη
After selecting the branch and clicking [Εύρεση], the system lists all
in-progress overtime entries for that branch. The user selects which entries
to terminate immediately, then [Προσωρινή Αποθήκευση] — this stages a
termination E8 for each selected entry, with f_to (end time) set to the
moment of staging + 2 minutes.
After [Προσωρινή Αποθήκευση], you have 2 minutes to review and click [Υποβολή]. If this window elapses without submitting, the staged termination is discarded and the mass-termination process must be restarted from [Εύρεση].
This is currently a portal-only workflow (no documented dedicated REST
endpoint) — equivalent results via the API would require submitting
individual OvTime termination entries.
Validating your XML
If you're producing XML for upload, validate it against the provided XSD before submitting. A simple free tool is Notepad++ with an XML plugin (e.g. XML Tools), which will highlight schema violations.