Skip to main content

Getting Started

This document is a guide for "Getting Started govgr", part of the technical documentation for developers implementing solutions in the gov.gr ecosystem.

It describes the basic steps a developer must follow to start building gov.gr applications that interoperate with the Greek government.

Introduction

Gov.gr supports a set of APIs and authentication flows that allow:

  • Social login via GSIS
  • Access to citizen/employee data via SOAP APIs
  • Authentication via OAuth2 or OpenID Connect

Creating a New Application

To get started:

  • Apply for credentials (client ID/secret or username/password) from the Interoperability Center KED
  • Request access for:
    1. GSIS authentication (OAuth/OpenID)
    2. Web Services (EMEP, SOE, AADE)
    3. Test Environment URLs

For developers in the proof-of-concept or testing phase, you can request sandbox access.

Environments

Environment overview:

  • Test: https://test.gsis.gr/...
  • Production: https://ked.gsis.gr/...
  • Redirect URI: https://<app-url>/authorize or /admin/authorize

Credentials are valid only for the specified environment.

Mandatory Audit Trail

All calls to State APIs (e.g., EMEP, AADE) must include:

  • auditTransactionId
  • auditTransactionDate
  • auditUnit
  • auditUserId
  • auditUserIp

This is a legal requirement and a technical prerequisite for APIs to function.

  • social-auth-gsis for Django OIDC/OAuth
  • next-auth + jwt-decode for Next.js
  • xmltodict and requests for SOAP integration with Python

Support

If you're facing technical issues or need debugging help:


We'd love your feedback
Was this helpful?