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
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
Segment export returns structured user-profile JSON records.
Braze segment user-profile export ↗
Export user profile by segment · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
Segment export creates downloadable multi-file JSON output.
Braze segment user-profile export ↗
Export output format · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
Segment and user_last_updated_at filters select exported profiles.
Braze segment user-profile export ↗
Request parameters / user_last_updated_at · Checked 2026-10-16
Access cost barrier -
-
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
The reviewed Braze route does not establish access cost barrier.
Braze segment user-profile export ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
Named Zapier integration does not establish arbitrary chosen-third-party eligibility.
Braze Zapier integration requirements ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Downstream permission -
-
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
The reviewed Braze route does not establish downstream permission.
Braze segment user-profile export ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
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
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
users/track creates or updates profiles and records events/purchases.
Braze create and update users ↗
Create and update users / Prerequisites · Checked 2026-10-16
Custom application path -
-
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
The reviewed Braze route does not establish custom application path.
Braze segment user-profile export ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
user_last_updated_at supports selected incremental profile exports.
Braze segment user-profile export ↗
Request parameters / user_last_updated_at · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
Endpoint defaults, contract variation and 429/reset guidance published.
Braze API rate limits and recovery headers ↗
Rate limits by request type / Troubleshooting429 · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
Modified profile export filter exists; deleted-profile identities unresolved.
Braze segment user-profile export ↗
user_last_updated_at · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
Re-enumerate current records to rebuild the disclosed scope; historical event replay, deletion recovery and full history are unverified.
Braze segment user-profile export ↗
Export user profile by segment · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 10.0/10
Original objects or portable records delivered to a customer-selected destination
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
JSON exports download or write to configured customer cloud storage.
Braze segment user-profile export ↗
Export output format / Credentials-based response details · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
The reviewed Braze route does not establish post-cancellation access.
Braze segment user-profile export ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
Profile records portable; selected event/history fields limited to 90 days.
Braze segment user-profile export ↗
Important /90-day data fields · Checked 2026-10-16
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
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
External applications consume exports and submit user updates.
Braze create and update users ↗
Create and update users · Checked 2026-10-16
Rights to custom logic -
-
Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products.
The reviewed Braze route does not establish rights to custom logic.
Braze segment user-profile export ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
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
Workspace REST keys require permissions for each endpoint. A documented named partner integration demonstrates one third-party path, but does not establish unrestricted eligibility for arbitrary applications.
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
Segment export writes files to a temporary download URL or configured customer cloud storage. Custom events, purchases and received campaign/Canvas fields contain only the last 90 days.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Workspace endpoint-scoped REST key | API key | Customer | Not confirmed | customer creates key with export/users.track permissions; general third-party eligibility and plan conditions unresolved | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Current endpoint defaults and runtime quota headers are documented, while users/track budgets vary by contract. Minimum API entitlement and Currents charges remain unresolved and are not combined.
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
POST /users/track records events/purchases and updates profile attributes with users.track permission. Success can precede asynchronous completion; dependent operations need state verification.
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
Segment exports can filter user_last_updated_at. This supports profile refresh, without establishing deletion identities or a durable consumer replay 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 establishedBraze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. Modified profile export filter exists; deleted-profile identities unresolved. | Braze segment user-profile export ↗user_last_updated_atChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedBraze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. Re-enumerate current records to rebuild the disclosed scope; historical event replay, deletion recovery and full history are unverified. | Braze segment user-profile export ↗Export user profile by segmentChecked 2026-10-16 |
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
Profile JSON files can be downloaded or sent to configured S3, Azure or Google Cloud storage. This is a scoped record export (it does not recover every historical event or native Canvas definition).
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
External code can update profiles and consume exports. Native workflow authoring/ownership and independent execution were not established in the reviewed route; cancellation retrieval rights remain unresolved.
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 scopeBraze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. Segment export returns structured user-profile JSON records. | Braze segment user-profile export ↗Export user profile by segmentChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsBraze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. Segment export creates downloadable multi-file JSON output. | Braze segment user-profile export ↗Export output formatChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersBraze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. Segment and user_last_updated_at filters select exported profiles. | Braze segment user-profile export ↗Request parameters / user_last_updated_atChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. Named Zapier integration does not establish arbitrary chosen-third-party eligibility. | Braze Zapier integration requirements ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. The reviewed Braze route does not establish access cost barrier. | Braze segment user-profile export ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. The reviewed Braze route does not establish downstream permission. | Braze segment user-profile export ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainBraze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. users/track creates or updates profiles and records events/purchases. | Braze create and update users ↗Create and update users / PrerequisitesChecked 2026-10-16 |
| How can customers connect an application they build or choose? | -Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. The reviewed Braze route does not establish custom application path. | Braze segment user-profile export ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksBraze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. user_last_updated_at supports selected incremental profile exports. | Braze segment user-profile export ↗Request parameters / user_last_updated_atChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsBraze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. Endpoint defaults, contract variation and 429/reset guidance published. | Braze API rate limits and recovery headers ↗Rate limits by request type / Troubleshooting429Checked 2026-10-16 |
| Where can a usable data copy be delivered? | Original objects or portable records delivered to a customer-selected destinationBraze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. JSON exports download or write to configured customer cloud storage. | Braze segment user-profile export ↗Export output format / Credentials-based response detailsChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. The reviewed Braze route does not establish post-cancellation access. | Braze segment user-profile export ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedBraze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. External applications consume exports and submit user updates. | Braze create and update users ↗Create and update usersChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Braze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. The reviewed Braze route does not establish rights to custom logic. | Braze segment user-profile export ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedBraze REST user-profile segment exports and users/track writes using endpoint-scoped workspace keys; Currents and zero-copy sharing are separate unassessed products. Profile records portable; selected event/history fields limited to 90 days. | Braze segment user-profile export ↗Important /90-day data fieldsChecked 2026-10-16 |
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-plan API entitlement and contract-specific charges
- Arbitrary third-party eligibility
- Deletion capture and retained replay
- Full history and native Canvas portability
- Post-cancellation retrieval rights
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.