Integrations

Connect your shop. Keep your data in sync.

Today it works with WooCommerce, PrestaShop, OpenCart, Magento and Shopware. Any other system, your own application or a CRM for example, connects through the API.

Azimea

API / SMTP / CSV

045° Platforms

Connect the platform you use.

Choose your store platform below. Each integration has its own setup steps and syncs the data needed for campaigns and automations.

  • WooCommerce Available

    Paste two REST keys from your WooCommerce admin. For abandoned carts, add the free Azimea plugin. You can revoke the keys at any time.

    How to connect
  • PrestaShop Available

    Open source, self-hosted, popular right across Europe.

    How to connect
  • OpenCart Available

    Open source and lightweight, still used by many long-standing shops.

    How to connect
  • Magento Available

    Adobe Commerce and Magento Open Source, for shops with large catalogues.

    How to connect
  • Shopware Available

    Connect Shopware 6.7 with the free Azimea app for newsletters, abandoned cart emails and post-purchase automation.

    How to connect

Automation integrations

  • n8n Cloud and self-hosted

    Create, update, find and unsubscribe contacts with the verified Azimea node for n8n Cloud and self-hosted n8n. Creating a profile does not subscribe it.

    Install and connect
Any system

No shop platform? Connect your own system.

Azimea is not tied to an online shop. Your own application, a CRM or an internal platform sends its people and what they do, and gets the same flows, campaigns, segments and reports.

Guide: connect your own system
  • Events

    What people do in your system: an account opened, a step finished, a payment made. Events start and stop flows and can count as results.

  • Contacts and consent

    People with your own fields and their consent, one at a time or 1,000 per call.

  • CSV import

    No developer yet? Bring your list in from a file, and add events later.

  • SMTP and webhooks

    Your system’s own emails go out through Azimea, and the delivery statuses come back to it.

090° How it connects

A key or a module, two minutes.

On WooCommerce, for example, you create a REST key with Read/Write permission and paste it into Azimea. The other platforms have their own short steps. We check the connection on the spot, then bring in your customers and orders, with no files and no exports.

  • Encrypted keys

    Once saved, they never appear anywhere: not in the interface, not in logs.

  • Light plugin, only for carts

    Customers and orders need nothing installed. The free plugin adds abandoned carts, without slowing your shop down.

  • Why Write as well

    So we can mark in your shop the orders that came from emails. We never touch products or prices.

  • Revoke any time

    Delete the access in your shop and the connection is cut instantly, without asking us.

All about the WooCommerce integration

180° Can’t see your platform?

Tell us what your shop runs on. We will email you when it is ready.

We count every request. The platform most shops ask for is the next one we build, and you hear first, with a single email.

In the meantime, your shop’s own emails (orders, passwords) can already go out through Azimea: over SMTP, with no code, from almost any platform, or through the API below if you have a developer.

We will email you once, when the integration is ready. We will not sign you up for anything else. Details in our privacy policy.

270° For developers

Send from your own code. Find out what happened.

Order confirmations, access codes, alerts: send them with a single HTTP call, from your shop’s verified domain. Azimea then tells you, through a signed webhook, when the email was sent, delivered, bounced, opened or clicked.

One email, one call

In the app, create an API key with the emails:send (send emails) permission. The key is shown only once, can have an expiry date and can be revoked at any time. Each key has its own rate limit, so one runaway integration cannot block the rest.

Emails sent through the API take the same route as all the others: through the queue, the suppression list and your account’s daily limit.

Request

curl https://api.azimea.com/v1/sending/emails \
  -H "Authorization: Bearer azm_live_7f3c…5e0c" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "emma@example.com",
    "subject": "Order #1043 is confirmed",
    "html": "<p>Thank you, Emma! Your parcel ships tomorrow.</p>"
  }'

Response · 200

{
  "isSuccess": true,
  "value": {
    "id": "3f2a9b61-6c0e-4d7a-9a51-0e8b1c2d4f10",
    "status": "Queued",
    "reason": null
  },
  "status": 0,
  "errors": []
}

Keep value.id: you will find it as message_id in every webhook about this email.

Signed webhooks

Give Azimea an address on your server and choose the events. You receive the whsec_… secret once; we keep only a hash of it.

Every notification is signed following the Standard Webhooks specification: HMAC-SHA256 over webhook-id.webhook-timestamp.body. You can verify the signature with the specification’s ready-made libraries. We recommend rejecting notifications older than five minutes.

If your server does not respond, we retry at growing intervals, from one minute to several hours. Delivery is “at least once”: a notification may arrive twice, with the same webhook-id, so you can spot the duplicate. From the app you can send a test notification, webhook.test, at any time.

  • email.sentHanded over to the sending server.
  • email.deliveredAccepted by the recipient’s server.
  • email.bouncedPermanently rejected by the recipient’s server.
  • email.complainedMarked as spam by the recipient.
  • email.openedOpened (once per email).
  • email.clickedA link in the email was clicked.

Notification received by your server

POST /webhooks/azimea HTTP/1.1
Host: your-shop.com
Content-Type: application/json
webhook-id: 8c1d2e4f-51a7-4b0e-b3c9-2f6a7d8e9b01
webhook-timestamp: 1789814527
webhook-signature: v1,K5oZfzN95Z9UVu1EsfQmfVNQhnkZ2pj9o9NDN/H/pI4=

{
  "id": "8c1d2e4f-51a7-4b0e-b3c9-2f6a7d8e9b01",
  "type": "email.delivered",
  "created_at": "2026-09-19T10:42:07.1830000+00:00",
  "data": {
    "message_id": "3f2a9b61-6c0e-4d7a-9a51-0e8b1c2d4f10",
    "email": "emma@example.com"
  }
}

email.clicked also includes url, and email.bounced includes reason. Fields without a value are left out, not sent empty.

The full API documentation, with examples for every call: docs.azimea.com. No developer? The same emails can go out over SMTP: settings for WordPress, PrestaShop and other platforms.

000° Start today

Is your shop on the list? Connect it in two minutes.

14 days free, counted from the day you create your account. No card needed.

By continuing, you agree to the Terms.