Interactive API Explorer
Every public endpoint is browsable and runnable in your browser, generated directly from the live OpenAPI spec — so it never drifts from the actual API.
- Explorer: samreshuuu.ru/api/v1/developers/docs
- OpenAPI spec: samreshuuu.ru/api/v1/developers/openapi.json
Authenticating
Every request carries your API key as a bearer token:
A missing or invalid token returns 401; a valid token that lacks the required scope returns 403. See Errors & rate limits for the full status-code and error-code contract.
Generate a Client
The raw spec is standard OpenAPI 3 — feed it to any generator to scaffold a typed client.
The same spec works with any OpenAPI-aware toolchain — swap the -g target for python, go, java, and so on, or point tools like openapi-typescript at the URL directly.
What's in the public surface
The explorer covers sessions, documents, knowledge, tasks, executions, agents, models, and chat-completions. Connectors are not exposed over REST — reach them through the agent (via chat) or the connector_execute tool over MCP.
Rate limits at a glance
The API enforces a per-minute request limit, shared across the organization:
| Field | Type | Description |
|---|---|---|
| Free | 10 req/min | Shared across the organization. |
| Pro | 30 req/min | Shared across the organization. |
| Max | 60 req/min | Shared across the organization. |
Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset; a 429 adds Retry-After. Full retry guidance is in Errors & rate limits.
FAQ
What does the interactive API explorer cover?
Every public REST endpoint — sessions, documents, knowledge, tasks, executions, agents, models and chat-completions — browsable and runnable in the browser, generated from the live OpenAPI spec so it never drifts from the real API. Connectors are not part of the REST surface; reach them through the assistant or the connector tools.
How do I authenticate a request?
Pass your API key as a bearer token in the Authorization header — Authorization: Bearer YOUR_API_KEY. A missing or invalid token returns 401; a token without the required scope returns 403.
Can I generate a typed client from the API?
Yes. The spec at /api/v1/developers/openapi.json is standard OpenAPI 3 — feed it to any generator (openapi-generator, openapi-typescript, …) to scaffold a typed client in your language.
Are there rate limits on the API?
Yes — a per-minute request limit shared across the organization (Free 10, Pro 30, Max 60 req/min). Responses carry X-RateLimit-* headers, and a 429 includes Retry-After. See Errors & rate limits for the full contract.
Frequently asked questions
What does the interactive API explorer cover?
Every public REST endpoint — sessions, documents, knowledge, tasks, executions, agents, models and chat-completions — browsable and runnable in the browser. It is generated from the live OpenAPI spec, so it never drifts from the real API. Connectors are not part of the REST surface; reach them through the assistant or the connector tools.
How do I authenticate a request?
Pass your API key as a bearer token in the Authorization header — Authorization: Bearer YOUR_API_KEY. A missing or invalid token returns 401; a token without the required scope returns 403.
Can I generate a typed client from the API?
Yes. The spec at /api/v1/developers/openapi.json is standard OpenAPI 3 — feed it to any generator (openapi-generator, openapi-typescript, and so on) to scaffold a typed client in your language.
Are there rate limits on the API?
Yes — a per-minute request limit shared across the organization (Free 10, Pro 30, Max 60 req/min). Responses carry X-RateLimit-* headers, and a 429 includes Retry-After. See Errors & rate limits for the full contract.