Workspaces
Get projects within a specific workspace
AuthorizationBearer <token>
OAuth 2.1 authorization code flow with PKCE (required of every client, public or confidential). Scopes are a ceiling on the credential, not a grant of access: a token also cannot exceed what the user who approved it may already do. A write scope does not imply its matching read — ask for both.
In: header
Scope: workspaces:read
Path Parameters
workspaceId*string
Unique identifier of the workspace.
Match
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$Format
uuidQuery Parameters
sort?
Sort directions per field (1 ascending, -1 descending).
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/workspaces/497f6eca-6276-4993-bfeb-53cbbbba6f08/projects"[ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "workspaceId": "ef0efa32-d1c1-43d4-a5e2-fe7b4f00403c", "name": "string", "slug": "string", "color": "string", "logo": "3c06f846-1ab1-40a9-8645-a19a9fdeae85", "settings": {}, "status": "active", "createdAt": 1678886400000, "updatedAt": 1678886400000 }]