📧 Email Sending

What is it?

A managed email-sending service for developers and technicians: create an API key from your account, then send via POST /api/mail/send. We handle the sending servers, reputation, queueing and retries — you focus on your product.

API example

Create your key from your platform account (the full key is shown only once), then:

curl -X POST https://securecelleouatine.com/api/mail/send \
  -H "Authorization: Bearer elm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"to":"[email protected]","subject":"Order confirmed",
       "text":"Hello, your order is confirmed.","from_name":"My Store",
       "reply_to":"[email protected]"}'

Quick reference:

{"ok":true,"data":{"message_id":"<[email protected]>","log_id":123}}

POST /api/mail/send — Bearer elm_… · POST /api/mail/keys · GET /api/mail/keys · POST /api/mail/keys/:id/revoke (session)

Quotas & limits

• Default quota: 100 emails/day per key (raisible by the administration).
• Rate limit: 20 emails/minute per key.
• One recipient per call, 200-char subject max, 500KB body max.
• Internal send queue — when full, the call is temporarily refused (429), never silently lost.

Sender (From) policy — stated plainly

Every email is sent from EL OUATINE’s verified identity — you cannot spoof another sender address, and that is intentional: it protects sending reputation for everyone. Allowed: from_name (display name, e.g. your store) and reply_to (your reply address — replies reach you directly).

Deliverability: what we promise and what we don’t

We send through trusted Gmail infrastructure (valid SPF and DKIM for our sender identity), but nobody can guarantee 100% delivery — here is the truth:

• No DNS setup needed: because the sender is our verified identity, SPF and DKIM just work.
• Sending from your own domain (e.g. [email protected] as the sender) is not supported yet — recommended alternative: from_name with your store name + reply_to with your address.
• Delivery also depends on your content and recipients’ filters — avoid aggressive wording and shady links.
• We monitor failures automatically: past the bounce threshold, the key is frozen immediately to protect everyone.

Anti-spam — red line