E-mail routing platform · API-first

Route your e-mail series without giving up compliance.

Missivia takes a contact, its consent acts and a sequence, and delivers every message itself — from a certified health-data host in France, with no third-party sender in between. Your tools talk to one API; your recipients get exactly what they agreed to.

Open the console OpenAPI contract

HDS-certified hosting, France
No third-party ESP
Consent per purpose
Multi-tenant, one key per tenant

PUT /v1/contacts
Authorization: Bearer rt_live_…
Idempotency-Key: 7f1c…

{
  "email": "lead@example.com",
  "first_name": "Camille",
  "consents": [
    { "purpose": "marketing_email", "status": "granted",
      "at": "2026-09-07T14:32:00Z", "source": "form:landing",
      "proof_url": "https://proofs.example.com/abc" }
  ],
  "subscriptions": [{ "list_id": "lst_…" }]
}

→ 201  the contact enters the sequence;
       the first message is queued within a minute.

What it does

One platform, three ways to send

Series that follow a contact over time, one-shot campaigns to a population, and single service e-mails — each under its own compliance regime, never mixed.

Contacts and consent register

A contact carries a register of consent acts, one per purpose: status, date, source, proof, wording of the box ticked. A refusal is kept as proof, never applied the other way round.

Sequences

A trigger (list, segment, API) and a graph of steps: send, wait, condition, webhook, A/B test, parallel branches. One step message, one send at most — workers are idempotent.

Campaigns and transactional

A marketing template to a list or a segment, once, with an audience preview. Or a single service e-mail — receipt, password reset — under contractual basis, never measured.

Built-in delivery

Messages are handed directly to the recipients’ mail servers, from the platform’s own IPs, with per-IP warm-up, SPF/DKIM/DMARC checks, bounce and complaint handling.

Webhooks and exports

Signed HTTPS deliveries with retries, anti-SSRF checks and no personal data in the body. Statistics and event-log exports, on demand or scheduled, CSV or JSON.

Console and sandbox

A multi-tenant web console with roles, two-factor authentication and a Sandbox mode where nothing leaves: captured e-mails, simulated bounces, safe integration.

Compliance by construction

Two pixels, never the same regime

An e-mail may carry two tracking pixels that look alike technically and have nothing in common legally. Missivia keeps them apart — and shows the consenting population next to every open rate.

	Deliverability pixel	Performance pixel
Regime	Exempt from consent	Subject to consent
Inserted	If the template enables it	Only with a valid open-tracking consent at render time
What is written	The last-open date, to the day, overwritten	An open event and the day’s aggregate
Never kept	IP, user agent, precise time, history	IP, user agent
Purpose	Adapt frequency, stop writing to inactive contacts	Measure performance, on consenting contacts only

Data-subject rights, built in

Unsubscribe link in every marketing e-mail, one-click (RFC 8058) and List-Unsubscribe — immediate effect.
Erasure: physical deletion, anonymised events, only a fingerprint kept to prevent accidental re-subscription.
Access and portability: one call returns attributes, consents, subscriptions, enrollments and events.
Retention periods enforced by the platform, adjustable per tenant.

No data leaves the perimeter

Hosted on a certified health-data (HDS) infrastructure in France.
No third-party e-mail service provider: the platform delivers itself.
Webhook bodies and exports contain opaque identifiers only — never an address.
Logs without e-mail addresses; API keys hashed; tracking tokens signed.

API-first

Five calls to your first lead

The console never does more than the API. Everything is a resource with an opaque identifier, cursor pagination, idempotent creations and RFC 9457 errors with a stable business code.

Create a list — the entry point of contacts and the most common trigger.
Create a template — the unsubscribe link is mandatory for marketing content; the sender domain must be verified.
Create and activate a sequence — send, wait, send…
Push the contact with its consent acts and its subscription, in one upsert.
Read its state — status, lists, enrollments, last event.

Download the OpenAPI contract

HTTP/1.1 422 Unprocessable Content
Content-Type: application/problem+json

{
  "type": "…/errors/contact_optin_missing",
  "title": "Contact has no valid opt-in consent",
  "status": 422,
  "detail": "purpose: marketing_email",
  "code": "contact_optin_missing",
  "request_id": "req_3f2a…"
}

# Every refusal has a stable code.
# The console explains each one:
# what triggers it, what to do.

GET /v1/stats/overview?from=2026-09-01&to=2026-09-07

{
  "sent": 48210, "delivered": 47655,
  "bounced_hard": 212, "bounced_soft": 343,
  "complained": 9, "unsubscribed": 127,
  "performance": {
    "consented_population": 12480,
    "opened": 5311, "clicked": 842,
    "open_rate": 0.4256, "click_rate": 0.0675
  }
}

# Rates are computed on the consenting
# population — never on sends.

Deliverability

Reputation is built here, IP by IP

With no provider to carry it, the platform manages its own sending reputation: progressive warm-up per IP and per domain, health monitoring per recipient family, automatic pause when bounce or complaint rates cross a tenant’s thresholds.

Sending domains verified (SPF, DKIM, DMARC) before the first send.
Daily warm-up caps that grow with reputation; deferral instead of failure when caps are reached.
Hard bounces and complaints go straight to the suppression list.
Inactive-contact handling based solely on the exempt deliverability signal.

A Dataventure product

Missivia is the e-mail routing layer behind Dataventure Group’s lead-collection tools, opened to partners as a multi-tenant platform. Each tenant gets its own space, keys, domains and quotas.