Skip to content
Radioso Docs home
Open app

API overview

Call the Radioso API to create workspaces, upload documents, and ask an agent a grounded question — the same work the dashboard does, reached over HTTP instead of a browser. One naming note before you dive in: the persona you configure in the dashboard is an agent. The chat surface you call to talk to it is still named assistant in API paths, such as /api/v1/assistant/chat. Same thing, two names — the assistant chat API is how you talk to an agent.

Get a token and ask a question

Sign in to the dashboard, open a workspace, and copy its token from Settings → API access, or reveal it over the API itself — see Workspaces and tokens. With a token in hand:

bash
curl -sS -X POST https://api.radioso.ai/api/v1/assistant/chat \
  -H "Authorization: Bearer $RADIOSO_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"message":"What can this workspace answer?","stream":false}'

Swap in https://api-us.radioso.ai for the US-hosted instance, or your own origin when self-hosting — a workspace token only works against the instance that issued it. If the workspace has no documents yet, the agent still answers, just without grounding; Documents and search covers giving it something to answer from.

Find your workflow

Three credentials, three jobs

Which credential you send determines which routes will accept the request:

  • Session cookie — set by login, invitation acceptance, or password reset. Manages accounts, users, invitations, and workspaces.
  • Workspace API token — sent as Authorization: Bearer <token>. Runs agents, skills, documents, chat, search, settings, and connectors.
  • Public token — a per-surface token embedded in a public chat link or website widget, not tied to your account. Handles anonymous chat and the Enterprise embed flow.

Exact schemas, status codes, and payload contracts live in the API Reference, generated from the OpenAPI document at backend/openapi.json — the canonical source for both that reference and this scenario-first section.

System endpoint

text
GET /health

Use it for service monitoring and basic deployment checks; it needs no credential.