Reference · built on requestConnectorMarketing, reviews & analytics

Braze

User profiles, events, campaigns, Canvas journeys, and subscription groups from a Braze workspace, with Currents event streaming.

Request accessPricing ↗

About

Braze is a customer engagement platform for email, SMS, push, in-app, and other channels. A workspace holds user profiles with attributes, custom events and purchases, segments, campaigns, Canvas journeys, subscription groups, and catalogs. Its REST API is served from a regional instance, such as rest.iad-01.braze.com for US-01, and every key carries explicit permissions per endpoint. Braze Currents streams engagement events to a warehouse or storage bucket.

Through Fibric, an operator reads profiles and events, joins them with orders, shipments, and support history, and proposes a user track call, a campaign or Canvas trigger, or a subscription change for your approval. Each approved call is made once and recorded with its reason.

This is a reference listing. It documents what Fibric would read from Braze and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • User profiles through POST /users/export/ids, by external_id, user_alias, email, phone, device_id, or braze_id, with fields_to_export
  • Campaign and Canvas details and analytics through the Export endpoints
  • Segment lists and segment analytics
  • Subscription group status for email and SMS
  • Engagement events streamed by Braze Currents in Avro to Amazon S3, Azure Blob, Google Cloud Storage, or a custom HTTP connector
  • Catalogs and their items

Proposed actions

  • Target capability: propose a custom event, purchase, or attribute update through POST /users/track, up to 75 objects per request
  • Target capability: propose an API-triggered campaign send through POST /campaigns/trigger/send, to up to 50 external_ids with trigger_properties
  • Target capability: propose a Canvas entry through POST /canvas/trigger/send
  • Target capability: propose a subscription group change through POST /subscription/status/set

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Start a delay journey when a shipment stalls

    When the carrier feed shows no scan for days, the operator proposes a Canvas entry for the affected users through /canvas/trigger/send. You approve the batch; each user enters once.

    With Stalled Shipment, ETA Notice

  • Watch for quiet accounts

    Currents events land in your warehouse. The operator reads who stopped engaging, joins that with orders, and proposes a custom event through /users/track that your win-back campaign listens for.

    With Churn Watch

  • Send an incident message to the right people

    The operator builds the recipient list from a segment and proposes an API-triggered campaign send with trigger_properties for the incident. Nothing sends until you approve.

    With Outage Notice

  • Record a support outcome on the profile

    After a low survey score and a callback, the operator proposes an attribute update through /users/track so campaigns can suppress or adapt.

    With Detractor Callback

Requirements

  • A Braze workspace and its REST endpoint, such as https://rest.iad-01.braze.com for US-01, shown under Settings > APIs and Identifiers
  • A REST API key with the permissions the operator needs, for example users.track, users.export.ids, and campaigns.trigger.send
  • An API-triggered campaign or Canvas built in the dashboard for each message the operator may propose
  • For event streaming, Braze Currents with Engagement Events entitlements, arranged through your account manager
Authentication
A REST API key sent as Authorization: Bearer, created in the dashboard with the permissions each endpoint requires, such as users.track or campaigns.trigger.send.

Limits

  • The default limit is 250,000 requests per hour per workspace; some endpoints carry their own, such as 250 per minute for /users/export/ids
  • /users/track varies by contract; data-point customers get a burst limit of 3,000 requests per three seconds
  • /users/export/ids takes at most 50 external_ids per call, and workspaces onboarded after August 22, 2024 must pass fields_to_export
  • Braze recommends a five-minute gap between dependent calls, because writes take time to settle

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Braze ↗

Questions and answers

Which URL does the connector call?
Your workspace's REST endpoint, which depends on the Braze instance. Examples in the docs include https://rest.iad-01.braze.com for US-01 and https://rest.fra-01.braze.eu for EU-01. The dashboard lists yours under Settings > APIs and Identifiers.
Does Braze push events to other systems?
Yes, through Braze Currents, a real-time stream of engagement events in Avro format to destinations such as Amazon S3, Azure Blob, Google Cloud Storage, Segment, mParticle, Tealium, or a custom HTTP connector. It is included in many pro and enterprise packages and needs Engagement Events entitlements.
How many users can one send request address?
Up to 50 external_ids per call to /messages/send, /campaigns/trigger/send, or /canvas/trigger/send, each with its own personalization, or a whole segment when broadcast is true. Broadcast sends are limited to 250 requests per minute.
Ask about Braze

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Braze through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy