API to create/update Segments

We have this same issue, as we have a segment that needs to have it's criteria changed at midnight every quarter. Real pain for whoever draws the short straw on NYE, you know?

So far, there's only one way I've found to successfully update a segment by api, and it's pretty clunky:

I used to use this back in the day with SFMC, but the Braze endpoints are a little more finicky:

If you use inspect mode in your browser, while on the network tab you save an update to the segment in question. From the network tab you'll be able to copy the actual request to Braze that includes your users authentication. 

You can import that into postman, curl etc and modify as you see fit. It should work until your user auth tokens expire.

Note: There are a ton of problems with this: It basically tricks Braze into thinking you're in your browser and clicking the buttons, so of course permissions are only scoped to that user, there are issues with how you authenticate users (SSO, IP whitelisting etc), issues if they ever change anything in the format of the api call etc. This basically works when you know you have one specific thing to do later this evening... But it DOES work.

Hi pcapazzi 

Have you had a look at the Braze docs for APIs, there is quite a lot of good info in there? Here's a couple of links that are relevant for your use case:

API Segment Identifier
You will find the API identifiers search at the bottom of the Settings -- > APIs and Identifiers page

REST API Permissions --> then click on Segments

Let us know if this is what you are after. 😊

Gotcha. Great product suggestions indeed. 😊

Why do you need to export this segment of users? I wonder if we knew more about what you're achieving, there might be another solution.

This is perhaps something that could be implemented as a webhook campaign and Braze could push the data to a destination.

Can you use currents or the snowflake integration? That would let you dump all the data and query it externally.

Regardless of anything though, there is a clear gap in the API.

If Braze were to create such an endpoint, I feel that they'd want to implement it such a way that it maintained feature parity with the segments in the UI - which is presumably a more challenging thing to implement. I wonder though if it could be limited to those only defined by SQL, which would keep things simple from an implementation standpoint.