Currently, whenever a user hits a limit or gate of some sort, they are usually presented with a generic 400/403 response with little guidance on where to go next.
The CLI uses heuristics to make a best guess, but this approach is not very scalable.
We'd like to standardise these errors so API clients can better infer the context, and properly inform the users.
Flagsmith has two kinds of limits:
Currently, whenever a user hits a limit or gate of some sort, they are usually presented with a generic 400/403 response with little guidance on where to go next.
The CLI uses heuristics to make a best guess, but this approach is not very scalable.
We'd like to standardise these errors so API clients can better infer the context, and properly inform the users.
Flagsmith has two kinds of limits:
"code": "invalid-plan", and direct to https://www.flagsmith.com/pricing in the human-readable description."code": "system-limit", and descriptions should direct to https://docs.flagsmith.com/support#getting-in-touch.