Overview
Project transactional email: templates, test sends, delivery history, lists, and campaign reads against the configured email provider.
API
{pe} = /projects/{projectId}/environments/{environmentId}.
| Method | Path | Notes |
|---|---|---|
| GET | /email/health | Health |
| GET/POST | /email{pe}/templates | RequireAuthorization |
| PUT/DELETE | /email{pe}/templates/{templateId} | RequireAuthorization |
| POST | /email{pe}/send-test | RequireAuthorization |
| GET | /email{pe}/deliveries | RequireAuthorization |
| GET | /email{pe}/lists | RequireAuthorization |
| GET | /email{pe}/campaigns | RequireAuthorization |
Clients
| Package | Runtime |
|---|---|
@vijihub/email | server |
VijiHub.Email | .NET |
Implementation
- Enable Email and configure a provider (Smtp, Postmark, Mailgun, SendGrid, Resend, AwsSes, or logging in Development).
- Create templates, send tests, and monitor deliveries.
- Platform auth emails (confirm/reset) are separate Identity flows handled by the platform email path in Development.
Constraints
- Project email APIs require authorization (JWT).
- Provider credentials stay in environment settings.
- Respect provider sending limits and domain authentication (SPF/DKIM) outside VijiHub.