MailerLite
MARKETING · EMAIL
Subscribers, groups, campaigns, and automations in their own account.
Connect MailerLite with Fabriq Developer
Your user pastes their MailerLite credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting MailerLite in practice
Import endpoints sit on their own limit — 5 requests a minute against the general 120 — and a batch request containing only subscriber upserts counts as an import, so the fastest-looking way to load a list is the slowest one MailerLite allows. API keys also belong to the person who created them and stop working if that user is removed or deleted from the account.
Scopes that draw scrutiny
Bearer API keyThe single credential, sent as `Authorization: Bearer [YOUR_API_KEY]`. There are no scopes, and it is tied to the user who created it rather than to the integration.
Rate limits
- General: 120 requests per minute; over the limit returns 429.
- Import endpoints: 5 requests per minute, covering POST /api/subscribers/import, POST /api/groups/{group_id}/import-subscribers, and batch requests containing only subscriber upserts.
- Exceeding the import limit returns 429 with a Retry-After header.
Worth knowing
- The key dies with its creator: "API keys are tied to the user who created them. If that user is removed or deleted, the key stops working" — so offboarding an employee breaks the integration, and the failure looks like a 401.
- Pinning the API version is a dated header, `X-Version: 2038-01-19`, so an integration that omits it moves whenever MailerLite does.
- The base URL is https://connect.mailerlite.com/api, not a mailerlite.com host, and both Content-Type and Accept must be application/json.
- Batching does not buy throughput for imports: a batch of subscriber upserts is treated as an import and drops to the 5-per-minute lane.
Checked against MailerLite API documentation (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 MailerLite behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.