Skip to content
Connection Guide

Connect Braze Without Breaking the Audit Trail

Use this guide to connect Braze or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryCommunication
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Braze and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated read-only Braze workspace REST API key for the approved configuration endpoints.
  2. 2
    Store rest_endpoint and api_key securely, and add app_ids only when SDK authentication key inventory is required.
  3. 3
    Validate core list endpoints and any optional app-specific SDK-auth key lookups before enabling scheduled sync.
  4. 4
    Keep identity export and SCIM flows out of this baseline.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

api_key

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.