myDATA API integration for your e-shop or app, through a certified provider
myDATA API integration means your e-shop or app sends every order to Greece's tax platform for a document on its own, and gets the MARK and QR code back, with nobody typing anything. That's what I build: the code that connects your system to a certified e-invoicing provider, for example Wrapp.
I'm not an e-invoicing provider. The provider issues the document and sends it to myDATA under its own licence. I build the link between the provider and your system.
It costs €200 a year plus €200 one-off for the setup, plus 24% Greek VAT. You pay the provider's own plan to the provider, separately.
How does myDATA API integration work?
Four steps, all automatic once an order completes:
- OrderYour customer pays in your e-shop or app.
- ProviderMy code sends the order to the provider's API: document type, lines, VAT, payment method.
- myDATAThe provider issues the document and transmits it to AADE's myDATA platform.
- Back to the orderThe MARK and the QR link come back and are saved on the order, so you see them in your admin and the customer gets them by email.
If something is rejected, the order doesn't sit quietly without a document. The error is logged and you see it.
What are the MARK and the QR code?
The MARK is the unique registration number myDATA gives every document it accepts. AADE's API documentation calls it "Μοναδικός Αριθμός Καταχώρησης Παραστατικού" (myDATA REST API, AADE), and the same document describes a qrUrl field that programs use to draw the QR code. Wrapp's API page says it returns "MARK, UID, digital signature and QR, with optional PDF" (Wrapp).
In practice: the MARK proves the document went through, and the QR goes on the PDF or email your customer receives.
Why through a provider and not straight to AADE?
AADE takes documents through several channels. Its myDATA page lists e-invoicing providers, timologio, ERP, a special entry form and online tax mechanisms (myDATA, AADE). Invoices between businesses have their own rules about how they're issued, and a provider covers both those and retail receipts.
Technically, a system can also send straight to AADE's myDATA API through the ERP channel. The link I build goes through a provider instead, and the provider does the issuing under its own licence. Wrapp, for example, is an "AADE-authorized e-invoicing provider" with AADE code 029, according to its API page. Which document each sale needs, and how it's classified, is your accountant's call. I build it the way they set it.
Do you need a custom integration, or is a plugin enough?
If you run WooCommerce or Shopify, the provider's ready-made plugin is probably enough. Wrapp, for example, lists ready connections for Shopify, WooCommerce and Skroutz and charges €140 + VAT per order source per year for them (Wrapp price list). Then you don't need me, and I'll tell you so in my first reply. Paying for custom code that already exists off the shelf is wasted money.
A custom myDATA integration makes sense when there's no plugin, or the plugin isn't enough:
- A custom e-shop, say on Next.js or Medusa, that doesn't run on WordPress or Shopify.
- A subscription or booking platform where payment happens inside your own app. I build systems like that, for example a Pilates subscription platform and app.
- Your own admin panel or CRM with no ready connection to a provider.
- Flows the plugin doesn't cover: cancellations, credit notes, several shops in one system, orders from several sources.
If orders already pass through an automation tool, the call to the provider can sit there too. I write about flows like that in my n8n automation ideas.
If you're selling into Greece from abroad, check first with a Greek accountant whether you need myDATA documents at all. That's their call, not mine.
What the myDATA integration includes
Setup (€200 one-off):
- I read the provider's documentation and your system, and write down which order becomes which document, following your accountant's instructions.
- I build the link: order to the provider, MARK and QR back on the order.
- A cancellation or credit note when an order is cancelled, as your accountant sets it.
- Tests in a test environment before anything goes to production.
Every year (€200): I keep the link working. If a document is rejected, the provider changes its API or AADE releases a new version of its specs, I fix it.
How much does myDATA API integration cost?
| What | Price | With 24% VAT | Paid to |
|---|---|---|---|
| Setup | €200 one-off | €248 | Me |
| Keeping the link working | €200 a year | €248 | Me |
| The provider's plan | Their price list | Their price list | The provider |
I calculated the VAT column myself, at 24%.
For scale: according to Wrapp's price list, its plans start at €109 a year for up to 6,000 documents. I read that price list on 16 October 2026. You pick the plan by how many documents you issue and pay the provider directly.
What I've tested so far
On 8 October 2026 I sent a receipt for services (type 11.2 in AADE's document list) to myDATA's test environment. myDATA accepted it and returned a MARK and a QR code. Then I cancelled it, and the cancellation went through too.
That test went straight to AADE's API, in the test environment, not through a provider. In real work the provider issues the document. And I don't have a client running this in production yet. If you'd be the first, you know that now.
What I don't do
- I don't issue documents and I'm not a provider. The provider you choose issues them.
- I don't give tax advice. Document types, classifications and deadlines come from your accountant.
- I have no partnership with Wrapp. I mention it as an example because it has a public, documented API. I work with any certified provider that has an API.
FAQ
Are you a certified e-invoicing provider?
No. I'm a developer, and I build the myDATA integration between your e-shop or app and a certified provider. The provider issues the document and transmits it.
Do I need myDATA REST API credentials?
If a provider issues your documents, the provider does the transmission to myDATA. Registering for the myDATA REST API is for software that sends directly, the ERP channel. What exactly you declare in myDATA, settle with your accountant.
Does it work with WooCommerce?
Yes, but for WooCommerce the provider's ready plugin is usually enough. A custom link is worth it when the plugin doesn't cover something you need, or your e-shop isn't WooCommerce.
Which provider should I choose?
Any certified provider with an API that suits you and your accountant. I mention Wrapp because it publishes its API documentation and has a test environment. Nothing else ties me to it.
How much does myDATA API integration cost?
€200 one-off for setup and €200 a year to keep it working, plus 24% VAT. The provider's plan is paid separately, to the provider.
What happens when an order is cancelled?
The link sends a cancellation or a credit note to the provider, whichever your accountant sets, and updates the order. myDATA has its own call for cancelling a document, and I tested it in the test environment.
Do you have a client using it already?
Not in production yet. What I have is the test in AADE's test environment on 8 October 2026: a type 11.2 receipt, MARK and QR back, then a cancellation.
Tell me what your system runs on
Tell me what your e-shop or app runs on, which provider you use (if you have one) and what documents you issue. I'll tell you whether the provider's plugin is enough or you need a custom myDATA integration, and what it would cost in total.