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.
async, fully typed, and throw typed
errors on failure. Request and response
models are exported under the Apollo namespace.
Projects
Agents
Agent versions
Threads
The trace methods are the management twins of the messaging ones — same
shapes, same
thread_id rule, authenticated with
the organization API key instead of a publishable key:
project_id, agent_id, user_id,
external_id, created (one value, or two for a range), tool, rule, and
param.
List endpoints also take sort_by / sort_order and page[size] /
page[after] / page[before] for keyset pagination in either direction.
Threads and runtime versions
A thread lives on the runtime that created it — reads and renames name that runtime with theruntime_version selector (e.g. '0.8.0', the runtime
version the agent runs on; any value outside the 1.x family selects runtime
v2, and it doesn’t have to match the thread’s exact build):
agent_id, user_id, and created (with agent_id) apply — the
runtime v1–only filters return a clear 400 on the runtime v2 path:
runtime_version, read those.
Pagination
List methods return a page:results plus meta cursors.
requestOptions argument
(timeoutInSeconds, maxRetries, abortSignal, extra headers, extra
queryParams, and a per-call organizationApiKey override) — see
Best practices.