Reference · Credentials
MailerLite API credentials
Used by 2 BusyBot nodes.
mailerLiteApi 2 fields The MailerLite credential holds an API key from your MailerLite account, plus a switch for MailerLite Classic. Classic and the current platform are separate products with separate APIs, so the switch has to match the account you are actually using.
Fields
| Field | Type | Required | Notes |
|---|---|---|---|
API KeyapiKey | password | Yes | Your MailerLite API key. |
Classic APIclassicApi | string | No | Set to "true" to use the Classic API. |
Getting your credentials
- Sign in to MailerLite.
- Open the integrations area of your account settings and generate an API key.
- Copy the key and paste it into the credential’s API Key field.
- If your account is on MailerLite Classic, set the Classic API field to
true. Leave it empty for the current platform.
Permissions and scopes
The key carries the account’s access to subscribers, groups and campaigns. Rotate it if it may have been exposed.
Troubleshooting
- 401 Unauthorized on a valid-looking key — the Classic switch does not match your account. A Classic key against the current API fails, and vice versa.
- Subscriber not found — the address is not in the account, or it is in a group the operation did not target.
- Fields not saving — the custom field must already exist in MailerLite.
Frequently asked questions
What is the Classic API field for?
MailerLite Classic and the current platform are separate products with separate APIs. Set it to `true` only if your account is on Classic — a mismatch causes authentication to fail even with a valid key.
How do I know which one I am on?
Classic accounts sign in to the legacy MailerLite interface. If you are unsure, try the default first and only switch if authentication fails.
Does one key cover the node and the trigger?
Yes, both declare the same credential type.
Nodes that use MailerLite API
One credential works across every node below — create it once and reuse it.
Last updated . Spotted something wrong? Tell us.