Authenticate to the Statsig Console API with a Console API Key and list all feature gates in a project

Documented steps

1. Generate a Console API Key in the Statsig Console under Project Settings > API Keys. Console API keys are the most powerful key type with full CRUD access to the Console API, unlike Client keys (limited to /initialize and /log_event) or Server Secret keys (limited to /download_config_specs and /log_event).
2. All Console API requests are served from the API host https://statsigapi.net, not from docs.statsig.com or console.statsig.com.
3. Build the request: GET https://statsigapi.net/console/v1/gates
4. Add required header STATSIG-API-KEY: <your_console_api_key>.
5. Optionally add header STATSIG-API-VERSION: 20240601 - currently optional but documented as becoming required in a future version; omitting it uses the current version implicitly.
6. Optionally filter with query params: type (TEMPORARY/PERMANENT/STALE/TEMPLATE), tags, teamID, targetAppID, includeArchived, creatorID, limit, page.
7. Pagination defaults to limit=10, page=1 if not specified.
8. Send with Content-Type: application/json.
9. Parse the 200 response: { message, data: [gate objects with id, name, description, status, rules, owner, ...], pagination: { itemsPerPage, pageNumber, nextPage, previousPage, totalItems } }.
10. To page through all gates, loop increasing page until pagination.nextPage is null.
11. A 403 response looks like { "status": 403, "message": "Forbidden resource" } - check the key is a Console API key scoped to the right project.
12. Reference: https://docs.statsig.com/console-api/introduction and https://docs.statsig.com/api-reference/gates/list-gates