Braze

When connecting the Braze integration in Trelica you will be asked to provide a SCIM API Endpoint and SCIM token.

To find your SCIM API Endpoint navigate to Settings > Admin Settings > SCIM Provisioning in Braze.

You will have been shown your SCIM API token when you first configured SCIM provisioning, and should have saved it to a secure location. If you haven't yet configured SCIM provisionign in Braze you will be able to do so from the page mentioned above. 

When you configure SCIM in Braze you will be asked for a Service origin field. We recommend trelica.com but any value is acceptable as long as you enter the same value into Trelica when you connect.

Braze API limitations

Braze describes it's API as being a SCIM API. Many elements do not adhere to basic parts of the SCIM specification. This isn't a problem for Trelica per se, but it lacks an endpoint to list all Braze users, which is a significant limitation.

On the other hand Trelica is able to request data about individual users based on their email address.

Trelica takes the list of applications users in Trelica and then request information about each of these from Braze. This means that user coverage will be limited to the users Trelica already knows about.

If you are using Braze in conjuction with an IdP like Okta, and doing SAML2 single-sign on, then as long as Trelica is integrated with your IdP then you will get good user coverage. Failing that you can manually upload a list of users from Braze into Trelica.

Braze does support provisioning and deprovisioning so it's still worth connecting despite these compromises.