Skip to main content

Authentication

The Woes REST API uses workspace API keys. Create a key in Settings → Keys, copy the full secret once, and store it in your server-side secret manager.
Workspace API keys start with woesk_. Widget keys are public install identifiers and are not accepted by REST API endpoints.

Bearer Token

Pass the key in the Authorization header.

Try Requests In Mintlify

The generated Endpoint Reference pages include an interactive API playground. Paste your own woesk_ key into the Bearer token field, adjust the prefilled example parameters or JSON body, and click Send to run the call.
The playground runs against https://woes.dev. Use a test workspace key when creating conversations, messages, or issues from the docs.
Use a disposable, scoped test key in the docs playground. Do not paste a production integration key. Playground requests may transit the docs runtime when proxying is enabled. For production keys, run curl or SDK calls from your own backend and revoke playground test keys after use.

Quick API Examples

These examples use active public Woes API resources. The API key must be a workspace API key that starts with woesk_.

List conversations

Create a conversation

Add a message

See Conversations for every supported conversation endpoint, request field, and response shape.

List issues

Create an issue

See Issues for every supported issue endpoint, request field, and response shape.

List clients

See Clients for client aggregate fields, filters, and read-only boundaries.

List agents

See Agents for public agent metadata, widget keys, and read-only boundaries.

Security Rules

  • Keep woesk_ keys on your backend.
  • Do not put REST API keys in widget snippets or client-side JavaScript.
  • Revoke keys from Settings → Keys when rotating credentials.
  • Each key is workspace-scoped; it cannot read or write another workspace.
  • Valid REST API calls are tracked against the key that authenticated the request.

Error Responses

For 429 rate_limited, back off and retry after a short delay. Public REST API requests are rate-limited per workspace API key.
Last modified on June 29, 2026