Keep Unisender lists and campaigns in order from the chat

The agent works with Unisender through https://api.unisender.com/ru/api, where every call is a method name and the key travels as a request parameter. It reads mailing lists and contacts with their fields and tags, emails and templates, campaigns and statistics on deliveries, opens, clicks and unsubscribes. Out of that come the campaign breakdown by clicks, the picture across lists and the regular summary of how the base grew over a period.

Some of the data Unisender does not compute on the spot: contact exports and delivery statistics are queued and return a task identifier instead of a ready answer. The agent polls such a task until it is done and shows the finished figures rather than a half-empty export. The second subtlety is list size: unsubscribed and invalid addresses stay in the list with their own status, so the contact count and the count of real recipients will not match, and the agent separates them explicitly.

On the write side the agent creates lists and additional fields, subscribes and excludes contacts, assembles emails from templates and prepares campaigns. Bulk sending it never launches on its own: first a test send for review, then your confirmation with the list and the number of recipients named — and only then the campaign starts. Transactional emails and SMS follow the same order, and the agent re-reads the result after the send.

The key is one per account and is not split by section, so the agent sees the whole account — narrow access cannot be granted here, and the only way to revoke it is to reissue the key. The key travels as a parameter of every request, so a reissue cuts access off instantly and the agent says so rather than quietly returning zero. Contacts and statistics come back from Unisender in portions, and a long selection is read to the end by the agent itself. It holds the rate within ten requests per second, and when data or permissions fall short it says so directly.