Stable application API
Integrate once. Provider credentials stay out of customer applications, and a provider change does not force a product rewrite.
Private preview · Capture mode live
Give your application one stable API. TEJL handles provider integration, sender onboarding, delivery policy, suppressions, event normalization and day-two operations.
Honest status: the gateway and hosted capture environment work today. Production delivery, customer accounts and billing remain admission-gated and are not represented as live.
const message = await tejl.send({
from: "welcome@yourdomain.com",
to: "customer@example.com",
template: "welcome-v3",
data: { firstName: "Mia" }
});
One API
Provider-neutral
EU-first operation
Managed onboarding
Built for evidence
01 / The platform
Direct email APIs are inexpensive. Reliable transactional email is not. TEJL Send places policy, provider portability and operations between your application and the delivery network.
Integrate once. Provider credentials stay out of customer applications, and a provider change does not force a product rewrite.
Required idempotency keys, tenant boundaries, quotas and sender policies stop common duplication and misuse paths.
Bounces, complaints and manual suppressions become normalized product state instead of scattered provider-specific logic.
TEJL owns onboarding runbooks, configuration review, monitoring, incident response and delivery-provider coordination.
Current message bodies are neither persisted nor returned. Logs redact authorization, webhook secrets and request payloads.
Capture mode exercises the real acceptance path without external delivery. Production is enabled only after its gates pass.
02 / Integration
Receive a tenant-scoped credential, SDK guidance and test sender policy.
Run your real application flow without sending externally or risking customer inboxes.
Verify domains, DNS, templates, events, complaint handling and production-provider access.
TEJL monitors the gateway and handles routine delivery infrastructure work under the selected service tier.
curl https://tejl-send.tejl.com/v1/messages \
-H "Authorization: Bearer <tenant-key>" \
-H "Idempotency-Key: order-1842-receipt" \
-H "Content-Type: application/json" \
--data '{
"from": "receipts@yourdomain.com",
"to": ["customer@example.com"],
"subject": "Your receipt",
"text": "Thank you for your order."
}'
{ "status": "captured", "replayed": false }Current API: raw HTML/text message submission, status lookup, usage and suppressions are implemented. Template APIs, SDKs and customer-managed configuration are roadmap items.
03 / Reliability model
04 / Commercial model
Private-preview pricing is a managed-service proposal, not a commodity email markup. Final limits and SLAs will be validated with design partners before public sale.
Managed Core
Onboarding from €750
Reliability Design-partner focus
Onboarding from €1,500
Enterprise
Scoped onboarding
Preview assumptions exclude VAT and extraordinary provider, dedicated-IP or custom compliance costs. No card is collected on this site.
05 / Admission roadmap
Real authenticated acceptance, persistence, policy and event behavior without external email delivery.
Validate onboarding, templates, domain ownership, traffic shape, support expectations and willingness to pay.
Enable only after sender identities, DKIM, MAIL FROM, provider production access, events and runbooks pass.
Accounts, RBAC, domains, templates, API keys, logs, usage and billing become customer-operable.
Contracted SLOs, audit evidence, disaster recovery, security controls and regional options.
06 / Questions
No. The hosted gateway is intentionally in capture mode. It accepts and records test traffic but sends no external email. Production admission is a separate verified step.
You can. TEJL Send is for teams that value a stable application contract and want sender onboarding, policy, events, monitoring and provider operations handled as one managed layer.
No. Login, dashboard, documentation portal and customer self-service controls on this page are non-functional pre-launch previews. They never ask for credentials.
Not yet. The core gateway proves important boundaries, but enterprise readiness requires the queued delivery architecture, observability, customer administration, compliance evidence and operational gates listed above.
Design partner intake / 2026