# Connect desktop activity capture

Source: https://www.tracktimer.app/docs/activity-context

Verify an activity-enabled API key and retrieve its workspace and assigned project profiles.

`GET /api/v1/activity/context`

Required scope: `activity:classify`

## Request

GET https://www.tracktimer.app/api/v1/activity/context with Authorization: Bearer YOUR_API_KEY. No body or query parameters. Requires activity:classify; replace older keys that lack this scope.

## Response — 200

```json
{"workspace":{"id":"example-workspace","name":"My workspace"},"projects":[]}
```

Returns {workspace:{id,name},projects:[{id,name,context}]}. Profiles use canonical project UUIDs and client/project names from the key owner's assigned, active projects in the bound workspace. Up to the first 100 projects, sorted by client and project name, are included. An empty project list is valid. This request makes no AI call and writes no time entries.

## Privacy and errors

Responses are private and no-store. The shared per-key quota is 120 requests per 60 seconds. Authentication/scope failures use 401/403; rate limits use 429. See [authentication](https://www.tracktimer.app/docs/authentication) and [errors and retries](https://www.tracktimer.app/docs/errors-and-retries).

Examples use illustrative IDs and data. Use the values returned by your own workspace. [Review error handling and retry behavior.](https://www.tracktimer.app/docs/errors-and-retries)