Skip to content

Environments & API key

There are two completely separate environments, each with its own portal, its own account and its own API key.

Sandbox Production
Purpose Development and testing Real documents with tax validity
Base URL https://provider-dev.timologisi.online https://provider.timologisi.online
Portal developer.portal.timologisi.online portal.timologisi.online
Swagger provider-dev.timologisi.online/index.html provider.timologisi.online/index.html
Account Automatic, when you sign up After certification
Issuer VAT number (ΑΦΜ) The VAT number you entered at sign-up is activated automatically Each customer VAT number is activated after a contract and an authorization (Onboarding API)
Credits Test credits Bought from the portal
Data retention Documents are deleted after 30 days Permanent archiving

1. Create an account (sandbox)

  1. Open the sign-up form.
  2. Enter your email and VAT number.
  3. Confirm the account from the email you receive and set a password.
  4. Log in to the portal. Your API key is there.

From the portal you can also:

  • view and search the documents you issued,
  • view the authorized VAT numbers,
  • upload customer logos. The logoId you get goes in the additionalDetails.logoId field.
  • (production) buy credits and request activation of a new VAT number.

The sandbox sends real emails too

The PDF of each document is sent to recipients.email and to the delivery addresses that AADE returns for the recipient. Onboarding API emails are sent as well. So, when testing:

  • use a fictitious VAT number as the recipient (as in the ready-made examples), not the VAT number of a real business,
  • put only your own addresses in all email fields.

2. Authentication

Every call sends the key in the API-KEY HTTP header:

POST /api/v1/Provider/SendInvoices HTTP/1.1
Host: provider-dev.timologisi.online
API-KEY: <το κλειδί σας>
Content-Type: application/json
Result Meaning
401 Unauthorized with no body The header is missing, the key is wrong or inactive, or you are using a sandbox key in production (or the other way round).
401 with {"errors": ["You don't have the authority to send for this vat numbers ..."]} The key is correct, but the issuer's VAT number is not activated on your account.

Keep the key secret

The API key issues documents with tax validity and uses up your credits.

  • Do not put it in code that runs in a browser or in a public repository.
  • Store it encrypted, like the other credentials of your app.
  • If it leaks, contact us immediately so we can revoke it and issue a new one.

3. One key, many customers

As a software house, you use one API key for all your customers. Each document states which customer it is issued for through issuer.vatNumber. The provider checks that this VAT number is activated on your account. Credits are shared by all VAT numbers on the account.

4. Technical requirements

  • HTTPS / TLS 1.2+.
  • JSON in UTF-8. Field names are case-insensitive, but we recommend camelCase as in the examples.
  • Dates in yyyy-MM-dd format and times in HH:mm:ss format.
  • Decimals as JSON numbers with a point (124.25), with up to 2 decimals for amounts.
  • Special characters inside strings: escape them as JSON requires (\", \\, \n, \r, \t, \b, \f).
  • Timeout: we recommend at least 60 seconds for SendInvoices, because the call waits for the AADE response and for the PDF to be generated.