Dependency-light client
Uses the standard library for bearer authentication, workspace selection, JSON requests, and structured errors.
Client integration
Start with working clients
Use the public OpenAPI contract and dependency-light Python, JavaScript, and Java starters for OAuth-secured, workspace-aware API calls.
Current availability
Starter clients are available now
Fetch-based client
Supports Node and modern runtimes with workspace headers, idempotency keys, and structured response handling.
HTTP client starter
Uses Java's standard HTTP client for enterprise service integration without a mandatory framework.
Accurate release status
Starter source clients and the public OpenAPI contract are available. Versioned PyPI, npm, and Maven packages remain planned.
Open the API contractRecommended client shape
Keep cross-cutting behavior in one layer
Acquire, cache, rotate, refresh, and revoke credentials without exposing tokens to business code.
Serialize requests, parse structured errors, enforce timeouts, and attach request IDs.
Poll durable jobs, subscribe to events, resume processing, and surface terminal states.
Retry only safe operations with bounded exponential backoff, jitter, and idempotency keys.
Propagate trace context and record operation, latency, retry, and outcome attributes.
Separate documents, knowledge, media, workflows, batches, and administration.
Common contract
Consistent behavior across languages
Bearer token and audience supplied by the applicationExplicit team workspace headerStructured DocIntel errorsIdempotency keys for safe retriesRequest and trace correlationPublic OpenAPI as the generation source
SDK contract
Expected behavior
Never log tokens or full sensitive payloadsExpose request and trace IDsPreserve structured DocIntel errorsSupport cancellation and timeoutsHandle pagination and rate limitsModel asynchronous terminal states