The MailGenie API supports the web application and governed integrations. The production API origin is api.mailgenie.org.
Core resource families
- organizations and authorized users;
- contacts, lists, and suppression state;
- campaigns, sequences, and message content;
- sending accounts and provider connections;
- delivery events, reporting, and analytics.
Authentication and tenant scope
Clients must use the supported application authentication flow. A successful login does not authorize access to another organization, environment, or product.
Error handling
Consumers should distinguish:
- validation failures that require corrected input;
- authentication or authorization failures;
- provider failures and rate limits;
- unavailable or stale reporting data;
- server failures that may be retried only when the operation is idempotent.
Do not infer that an operation succeeded from an HTTP response alone. For send-capable actions, confirm the resulting campaign and provider-visible state while preserving idempotency.
Detailed endpoint reference will be added from the canonical API contracts after route inventory and tenant-scope review.