Skip to main content
Find the projects available to the signed-in user. Method: GET Path: /projects Use the HTTP base for your authorized environment and an Authorization: Bearer header. See authentication and HTTP setup.

​
Parameters

This table covers the standard read profile. It excludes internal application routes and advanced analysis controls. No path or query parameters.

​
Request example

Set IQRUSH_API_BASE and IQRUSH_ACCESS_TOKEN through secure configuration. Replace project/run IDs and sample selections with values returned by your account. JSON objects and arrays are encoded as query strings.

​
Read the response

Top-level projects contains project records. Read project_id, name, workspace_id, and workspace_name to select the intended project. count is the returned project count. Use returned IDs. A project name alone may not be unique. An empty list is not an authentication failure by itself.

​
Fields to use

These selected fields explain the example and the result to preserve. Field presence depends on the response; this is not a complete response schema. Selected response fields from IQRush Dev. Lists are shortened and project/run IDs are placeholders; this is not the full response.
Read the actual returned scope, counts, and interval levels before interpreting these fields. MCP equivalent: list_projects. Use the parameters and defaults on this page for HTTP.

​
If the result is unavailable

Check HTTP status and the response’s error field before using data. A successful empty response does not establish a zero value. Preserve not_available, not_available_reason, unavailable_reason, and linked where returned. Errors and recovery shows observed examples.