The EU Email API for Teams That Need More Than a Regional Endpoint
A modern REST email API operated by Infotech Pioneers Oy, a Finnish company subject to EU law. No US CLOUD Act exposure on the operator. Pre-signed Article 28 DPA, signed webhooks, sandbox key on signup, 1,000 free sends to evaluate.
1,000 free sends · No credit card · Pre-signed DPA · Node.js & Python SDKs
Quick Answer
An EU email API is a REST email-sending service where both the data processing and the operating company sit inside the European Union. Regional data residency alone (e.g. an “EU endpoint” from a US-incorporated provider) does not solve GDPR transfer concerns because the operator remains under foreign legal compulsion. NexusProMail is operated by Infotech Pioneers Oy, a Finnish company under EU law, with a pre-signed Article 28 DPA, signed-HMAC webhooks and suppression enforcement at the API layer. EU data residency is on the roadmap for Q3 2026.
Key Takeaways
- Operator jurisdiction (the company processing your data) often matters more for GDPR than data centre location
- US-incorporated providers retain CLOUD Act and FISA Section 702 exposure even with EU regional endpoints
- A pre-signed Article 28 DPA removes weeks of legal back-and-forth from procurement reviews
- Modern REST API: send, schedule, batch, contacts, segments, webhooks, suppression — same primitives as the US incumbents
- Sandbox API key on signup with 1,000 free sends per month — evaluate without committing DNS changes
Operator Jurisdiction vs Data Residency
Two distinct questions get conflated in many vendor evaluations. The first is where customer data physically sits. The second is which country's legal framework binds the company that processes it. For GDPR, Schrems II and most EU procurement reviews, the second question matters as much as the first.
Operator jurisdiction
Which country's laws govern the company controlling the platform. Determines whether US frameworks (CLOUD Act, FISA Section 702, NSL gag orders) can compel disclosure of customer data regardless of where it sits. For NexusProMail, the operator is Infotech Pioneers Oy — Finnish, EU-jurisdiction, outside US compulsion.
Data residency
Where customer data is physically processed and stored. Addresses GDPR Article 44 transfer requirements when set to an EU region. NexusProMail currently runs on AWS us-east-1; eu-west-1 (Ireland) migration is planned for Q3 2026. Processing today is governed by Finnish law regardless of physical region.
Sub-processor chain
The list of downstream processors that touch customer data — typically the cloud host, analytics vendors, and CDN. Published transparently. Each sub-processor change carries a notice period during which customers can object. The pre-signed DPA enumerates the current chain by reference.
What the API Actually Lets You Do
The API surface covers the full transactional and marketing email lifecycle. If you've integrated Mailgun, SendGrid, Postmark or Resend, the concepts will be familiar — different field names, similar primitives.
Send a single message
POST /v1/api/send with to, from, subject and html (or template_id). Returns immediately with a message ID for tracking.
Batch send
POST /v1/api/send/batch accepts up to 1,000 recipients per call with per-recipient variable substitution.
Schedule a future send
Pass a send_at ISO-8601 timestamp. The API queues the message and returns the scheduled ID — cancel until 5 minutes before send.
Contact + list management
CRUD for contacts, lists, segments and custom attributes. Bulk import via CSV up to 1M rows. Segment by engagement, custom field, lifecycle stage.
Webhook events
Register endpoints to receive delivered, opened, clicked, bounced, complained, unsubscribed events. Payloads HMAC-signed for authenticity.
Suppression enforcement
The API checks the suppression list before every send. Sends to suppressed addresses fail at the API layer with HTTP 422.
Template management
Store templates server-side with variable placeholders. Send by template_id with a per-call variables object — no client-side rendering needed.
Multi-domain sending
Configure multiple sending domains under one account, each with isolated DKIM keys and reputation. Useful for multi-brand or multi-product senders.
The Compliance Story EU Buyers Actually Ask About
EU procurement reviews for new processors tend to ask the same questions. We've published the answers up-front so legal and compliance reviewers can move through the gate without back-and-forth.
What It Costs
Contact + send-volume based pricing. The free tier covers small-volume transactional workloads completely; paid plans add headroom and product features.
Frequently asked questions
What makes an email API an "EU email API"?
How is this different from Mailgun's EU region or SendGrid's EU endpoint?
What does the REST API actually let me do?
Is a DPA included or does it need to be negotiated separately?
What languages and SDKs are supported?
What's the free tier?
Does the API enforce suppression lists?
What about EU data residency for the actual infrastructure?
Get a sandbox API key
Sandbox key issued on signup. 1,000 free sends per month. No credit card. DNS changes only when you cut over to production.
Start free — DPA included →Also read: Transactional email API · API pricing · Data Processing Agreement · Schrems II compliance · GDPR email marketing · SendGrid EU alternative · Mailgun EU alternative · Resend EU alternative