Skip to main content
ApolloManagementClient is the server-side client for operating your workspace. It authenticates with your organization API key, sent as the x-organization-api-key header on every request — never expose the key in the browser.
All methods are async, fully typed, and throw typed errors on failure. Request and response models are exported under the Apollo namespace.

Projects

Agents

Agent versions

Threads

Filter fields go directly on the request: project_id, agent_id, user_id, external_id, created (one value, or two for a range), tool, rule, and param.
Prefer a filter such as project_id over an empty request — the unfiltered list sorts every thread in the organization and can be slow. For large windows, raise the per-call timeout: client.threads.listThreads({ project_id }, { timeoutInSeconds: 120 }).

v2 threads

Threads created by agents on the v2 runtime (UUID thread ids) live on that runtime — reads and renames take the runtime_version selector (e.g. '0.8.0', the runtime version the agent runs on):
Listing v2 threads is always scoped to an agent or an end user, and only agent_id, user_id, and created (with agent_id) apply — v1-specific filters return a clear 400 on the v2 path:

Pagination

List methods return a page: results plus meta cursors.
Every method also accepts a final requestOptions argument (timeoutInSeconds, maxRetries, abortSignal, extra headers) — see Best practices.