Each project (or workspace) may be associated with a Harness organization and project, which are exposed through organizationIdentifier and projectIdentifier. You can use these filters instead of (or in addition to) the name query parameter when retrieving a workspace ID.

The result set of the API may be reduced based on the Project View Restrictions.

👍
Use this endpoint to get a workspace ID after migration to Harness
After migration to Harness, you can retrieve the workspace ID for a project by calling this endpoint and filtering results by organizationIdentifier and projectIdentifier.
Alternatively, filter by name using the Harness project name, not the Harness project ID. Your Split legacy API key will continue to work for this endpoint.
For detailed instructions, see the Retrieving a Workspace ID Using Harness Identifiers section in the Before and After: APIs for Split Admins Postman collection.

Access requirements

The Authorization Bearer (Admin API Key authorizing the request) must have one of the following roles and scopes:

Admin API Key roles accepted

API_ALL_GRANTED
API_ADMIN
API_WORKSPACE_ADMIN

Admin API Key scopes accepted

GLOBAL
WORKSPACE*
ENVIRONMENT*

* The result set of the API may be subject to reduction, restricting access to certain elements, if they are not accessible by the provided API key.

You can continue using your legacy Split Admin API key for this endpoint. To learn more about Admin API Key roles and scopes, see API keys overview.