Using the SMTP aggregation API

Several sending accounts behind one outbound path, rotated by the platform:

• Subscription-based: nothing sends without an active subscription, and quota covers both daily and monthly volume
• Three things must line up to send: a subscription in term, a usable sending account, and the currently valid API key
• Three ways to send: compose online, campaigns (throttling, tracking, scheduling) and API calls with several recipients per request
• Campaigns merge and deduplicate and drop the unsubscribe list; templates have variables substituted and unsubscribe links injected by the platform
• Common errors: 403 means an expired or inactive subscription, 429 means the daily or monthly quota is exceeded, and a reset key stops working immediately

Frequently Asked Questions

I subscribed but still cannot send.

Check three things in order: the subscription is in term, a usable sending account exists, and the API key in use is the currently valid one. Any one missing stops delivery.

Does a test mail use quota?

No. The page states that test sends do not count against sending quota, so you can try freely while configuring.

Related pages: Help Center · Guides & FAQ · SMTP Email API · High-Deliverability · Tovanix API Documentation