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
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
Brevo returns contact IDs, attributes and list membership through its contact collection.
Brevo contact collection ↗
offset, modifiedSince, createdSince and collection filters · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
Traverse contacts with offset and limit, keeping the selected list or segment and attribute filters consistent.
Brevo contact collection ↗
offset, modifiedSince, createdSince and collection filters · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
modifiedSince and createdSince select contact dates. listIds and segmentId are alternative collection selectors.
Brevo contact collection ↗
offset, modifiedSince, createdSince and collection filters · Checked 2026-10-22
Access cost barrier -
-
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
Brevo contact rate limits ↗
General contact RPH/RPS limits and Handling rate limit errors · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
The technical route is documented; eligibility and review for independently distributed third-party applications remain unresolved.
Brevo API-key authentication ↗
Create your API key, IP authorization and api-key header · Checked 2026-10-22
Downstream permission -
-
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
Brevo API-key authentication ↗
Create your API key, IP authorization and api-key header · 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
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
Create contacts with email or supported identifiers and the documented attributes. Consent and list behavior require explicit configuration.
Brevo create contact ↗
Contact identifiers and attributes · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
Brevo API-key authentication ↗
Create your API key, IP authorization and api-key header · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
modifiedSince supports incremental contact reads. This review does not establish deletion events or a retained change log.
Brevo contact rate limits ↗
General contact RPH/RPS limits and Handling rate limit errors · Checked 2026-10-22
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
General contact limits are 36,000 requests/hour and ten/second; higher tiers differ. Monitor rate-limit headers and retry after throttling.
Brevo contact rate limits ↗
General contact RPH/RPS limits and Handling rate limit errors · Checked 2026-10-22
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
Modified-date filtering identifies contact updates; complete scans are needed to reconcile missing records.
Brevo contact rate limits ↗
General contact RPH/RPS limits and Handling rate limit errors · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete 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.
Brevo contact collection ↗
offset, modifiedSince, createdSince and collection filters · 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
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
Brevo contact collection ↗
offset, modifiedSince, createdSince and collection filters · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
Brevo API-key authentication ↗
Create your API key, IP authorization and api-key header · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
Brevo contact collection ↗
offset, modifiedSince, createdSince and collection filters · 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
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
Brevo API-key authentication ↗
Create your API key, IP authorization and api-key header · Checked 2026-10-22
Rights to custom logic -
-
Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
Brevo API-key authentication ↗
Create your API key, IP authorization and api-key header · 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 an account API key and send it in the api-key header. Apply the account’s IP authorization settings; OAuth is a separate route.
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
Traverse contacts with offset and limit, keeping the selected list or segment and attribute filters consistent. modifiedSince and createdSince select contact dates. listIds and segmentId are alternative collection selectors.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| v3 contact collection and contact creation | API key | Customer | Not confirmed | Not confirmed | 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 contacts with email or supported identifiers and the documented attributes. Consent and list behavior require explicit configuration.
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
modifiedSince supports incremental contact reads. This review does not establish deletion events or a retained change log.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedBrevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. Modified-date filtering identifies contact updates; complete scans are needed to reconcile missing records. | Brevo contact rate limits ↗General contact RPH/RPS limits and Handling rate limit errorsChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedBrevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete 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. | Brevo contact collection ↗offset, modifiedSince, createdSince and collection filtersChecked 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 scopeBrevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. Brevo returns contact IDs, attributes and list membership through its contact collection. | Brevo contact collection ↗offset, modifiedSince, createdSince and collection filtersChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsBrevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. Traverse contacts with offset and limit, keeping the selected list or segment and attribute filters consistent. | Brevo contact collection ↗offset, modifiedSince, createdSince and collection filtersChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersBrevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. modifiedSince and createdSince select contact dates. listIds and segmentId are alternative collection selectors. | Brevo contact collection ↗offset, modifiedSince, createdSince and collection filtersChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | -Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. The technical route is documented; eligibility and review for independently distributed third-party applications remain unresolved. | Brevo API-key authentication ↗Create your API key, IP authorization and api-key headerChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | Brevo contact rate limits ↗General contact RPH/RPS limits and Handling rate limit errorsChecked 2026-10-22 |
| Which external write operations are documented? | Create and update in one business domainBrevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. Create contacts with email or supported identifiers and the documented attributes. Consent and list behavior require explicit configuration. | Brevo create contact ↗Contact identifiers and attributesChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionBrevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. The documented interface can connect customer application code within its authorization and resource scope. | Brevo API-key authentication ↗Create your API key, IP authorization and api-key headerChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksBrevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. modifiedSince supports incremental contact reads. This review does not establish deletion events or a retained change log. | Brevo contact rate limits ↗General contact RPH/RPS limits and Handling rate limit errorsChecked 2026-10-22 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsBrevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. General contact limits are 36,000 requests/hour and ten/second; higher tiers differ. Monitor rate-limit headers and retry after throttling. | Brevo contact rate limits ↗General contact RPH/RPS limits and Handling rate limit errorsChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsBrevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | Brevo contact collection ↗offset, modifiedSince, createdSince and collection filtersChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | Brevo API-key authentication ↗Create your API key, IP authorization and api-key headerChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedBrevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | Brevo API-key authentication ↗Create your API key, IP authorization and api-key headerChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | Brevo API-key authentication ↗Create your API key, IP authorization and api-key headerChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedBrevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction. | Brevo contact collection ↗offset, modifiedSince, createdSince and collection filtersChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Brevo / v3 contact collection and contact creation; message content, CRM objects, campaigns and complete account migration are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | Brevo API-key authentication ↗Create your API key, IP authorization and api-key headerChecked 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.