Frequently Asked Questions

Date of slack thread: 7/19/24

Anonymous: Hi Statsig. I see there is a PATCH endpoint for gate rules, but I don’t see a PUT/POST. Is there an api to create a single new rule for a given gate?

An Le (Statsig): hi <@U06L4SJ0KCM>, you are right we currently dont have those operations supported. We can put in feature request and prioritize to have them implemented for you.

Anonymous: Could you let me know if there’s a better usage pattern than what we’re doing now that might be supported for my use case?

My Goal: I want to create a button on my internal tool that turns on a gate for one of my customers

How we use statsig now: We have 1 rule per customer per gate. The rule enables 100% of users for which their orgId (custom field of ours) matches the account we want to target

How I expect to use the API: I can PUT a new rule onto a gate, including my customer orgId logic.

Anonymous: afaik we don’t use segments. i wonder if that could help

An Le (Statsig): if this gate is just to turn on off, could you add your new user to the same rule? like you can add a rule: if criteria unit id any of [list user], then pass 100%, else default fail

Then in ConsoleAPI you can update the gate rule instead of creating a new one

Anonymous: Yeah, I think that’s what we’ll end up doing. I was just hoping to have an operation that worked on a single customer at a time instead of needing to rewrite the full list. But this should work, thanks

An Le (Statsig): ah i see, the PATCH requires the previous list and update on it which is quite annoying, so you need to GET > PATCH. We will try to improve our PATCH ops in the future. Thank you for flagging it!

Anonymous: exactly!