Unisender
MARKETING · MARKETING
Contact lists, contacts, and email and SMS campaigns in the account they connected.
Connecting Unisender in practice
Unisender’s headline allowance is 1,200 requests per 60 seconds, but the methods an agent actually needs are metered separately and far tighter: sendEmail and getContactCount are 60 per 60 seconds and exportContacts is 20. Budgeting against the 1,200 figure will overrun the send path by twenty times.
Rate limits
- General limit: 1,200 requests per 60 seconds.
- sendEmail: 60 requests per 60 seconds. getContactCount: 60 per 60 seconds.
- exportContacts: 20 requests per 60 seconds.
- createCampaign: 100 per 60 seconds. subscribe: 300 per 60 seconds. checkEmail: 300 per 60 seconds. sendSms: 300 per 60 seconds.
Worth knowing
- Limits are per method, not per account, so a contact import and a campaign send draw on separate buckets and a single client-side limiter will be wrong for both.
- exportContacts at 20 a minute makes a full contact export the slowest operation in the API by an order of magnitude, so reconciliation jobs need to be incremental.
- createCampaign at 100 a minute is the real cap on any per-segment campaign automation, well under the general limit.
- The per-method limit table is published in the Russian-language reference; the English /en/support/api/ pages now return 410 Gone, so the authoritative numbers are at unisender.com/ru/support/api/common/api-limits/.
Checked against Unisender API request limits (2026-09-29), Unisender API method index (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Unisender behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.