OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
MailerLite returns subscriber fields, status and subscription timestamps through its current REST API.
MailerLite subscriber list and upsert ↗
List all subscribers, Request parameters and Create/upsert subscriber · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
Follow the subscriber collection’s cursor or links.next until exhausted. Include every required subscriber status.
MailerLite subscriber list and upsert ↗
List all subscribers, Request parameters and Create/upsert subscriber · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
filter[status] selects active, unsubscribed, unconfirmed, bounced or junk subscribers; group inclusion is optional.
MailerLite subscriber list and upsert ↗
List all subscribers, Request parameters and Create/upsert subscriber · Checked 2026-10-22
Access cost barrier -
-
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
MailerLite subscriber list and upsert ↗
List all subscribers, Request parameters and Create/upsert subscriber · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
Generate a bearer API token under Integrations. Keys are permanently bound to their creator and stop working when that user is removed.
MailerLite authentication and key lifecycle ↗
Authentication and API keys lifecycle · Checked 2026-10-22
Downstream permission -
-
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
MailerLite authentication and key lifecycle ↗
Authentication and API keys lifecycle · Checked 2026-10-22
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
Create or upsert a subscriber by email. Omitted fields and groups are preserved rather than removed.
MailerLite subscriber list and upsert ↗
Create/upsert subscriber: non-destructive updates · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
MailerLite authentication and key lifecycle ↗
Authentication and API keys lifecycle · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 5.0/10
Scheduled feeds or recurring extracts
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
MailerLite subscriber list and upsert ↗
List all subscribers, Request parameters and Create/upsert subscriber · Checked 2026-10-22
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
The general budget is 120 requests/minute; import creation has a separate five/minute limit. Use Retry-After and backoff after 429.
MailerLite authentication and key lifecycle ↗
Rate limits and Import rate limits · Checked 2026-10-22
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established.
MailerLite subscriber list and upsert ↗
List all subscribers, Request parameters and Create/upsert subscriber · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified.
MailerLite subscriber list and upsert ↗
List all subscribers, Request parameters and Create/upsert subscriber · Checked 2026-10-22
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
MailerLite subscriber list and upsert ↗
List all subscribers, Request parameters and Create/upsert subscriber · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
MailerLite authentication and key lifecycle ↗
Authentication and API keys lifecycle · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
MailerLite subscriber list and upsert ↗
List all subscribers, Request parameters and Create/upsert subscriber · Checked 2026-10-22
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
MailerLite authentication and key lifecycle ↗
Authentication and API keys lifecycle · Checked 2026-10-22
Rights to custom logic -
-
MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
MailerLite authentication and key lifecycle ↗
Authentication and API keys lifecycle · Checked 2026-10-22
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Generate a bearer API token under Integrations. Keys are permanently bound to their creator and stop working when that user is removed.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Follow the subscriber collection’s cursor or links.next until exhausted. Include every required subscriber status. filter[status] selects active, unsubscribed, unconfirmed, bounced or junk subscribers; group inclusion is optional.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| current subscriber REST API list and upsert | API key | Customer | No | Customer-supplied credentials | 2026-10-22 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Minimum plan and exact route fees remain unconfirmed.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Create or upsert a subscriber by email. Omitted fields and groups are preserved rather than removed.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedMailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established. | MailerLite subscriber list and upsert ↗List all subscribers, Request parameters and Create/upsert subscriberChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedMailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified. | MailerLite subscriber list and upsert ↗List all subscribers, Request parameters and Create/upsert subscriberChecked 2026-10-22 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can write external integration code. Native workflow rights and independent execution remain unresolved (record access does not establish portable application logic).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeMailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. MailerLite returns subscriber fields, status and subscription timestamps through its current REST API. | MailerLite subscriber list and upsert ↗List all subscribers, Request parameters and Create/upsert subscriberChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsMailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. Follow the subscriber collection’s cursor or links.next until exhausted. Include every required subscriber status. | MailerLite subscriber list and upsert ↗List all subscribers, Request parameters and Create/upsert subscriberChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersMailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. filter[status] selects active, unsubscribed, unconfirmed, bounced or junk subscribers; group inclusion is optional. | MailerLite subscriber list and upsert ↗List all subscribers, Request parameters and Create/upsert subscriberChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalMailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. Generate a bearer API token under Integrations. Keys are permanently bound to their creator and stop working when that user is removed. | MailerLite authentication and key lifecycle ↗Authentication and API keys lifecycleChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | MailerLite subscriber list and upsert ↗List all subscribers, Request parameters and Create/upsert subscriberChecked 2026-10-22 |
| Which external write operations are documented? | Create and update in one business domainMailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. Create or upsert a subscriber by email. Omitted fields and groups are preserved rather than removed. | MailerLite subscriber list and upsert ↗Create/upsert subscriber: non-destructive updatesChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionMailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. The documented interface can connect customer application code within its authorization and resource scope. | MailerLite authentication and key lifecycle ↗Authentication and API keys lifecycleChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsMailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review. | MailerLite subscriber list and upsert ↗List all subscribers, Request parameters and Create/upsert subscriberChecked 2026-10-22 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsMailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. The general budget is 120 requests/minute; import creation has a separate five/minute limit. Use Retry-After and backoff after 429. | MailerLite authentication and key lifecycle ↗Rate limits and Import rate limitsChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsMailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | MailerLite subscriber list and upsert ↗List all subscribers, Request parameters and Create/upsert subscriberChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | MailerLite authentication and key lifecycle ↗Authentication and API keys lifecycleChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedMailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | MailerLite authentication and key lifecycle ↗Authentication and API keys lifecycleChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | MailerLite authentication and key lifecycle ↗Authentication and API keys lifecycleChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedMailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction. | MailerLite subscriber list and upsert ↗List all subscribers, Request parameters and Create/upsert subscriberChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -MailerLite / current subscriber REST API list and upsert; Classic API, campaign bodies, attachments and full account migration are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | MailerLite authentication and key lifecycle ↗Authentication and API keys lifecycleChecked 2026-10-22 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Minimum commercial entitlement and exact API charges
- Downstream contractual permissions and post-cancellation retrieval rights
- Complete migration of history, files, permissions and native workflow definitions
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.