API keys
An API key authenticates requests made against Woise's API on your organization's behalf, for anything you'd rather script or integrate than click through in the dashboard — triggering a workflow run, for instance.
Creating and revoking a key
Keys are created and archived from the API keys page. A key is shown to you once, at creation time, and cannot be retrieved again afterward — if you lose it, archive it and create a new one rather than trying to recover the original value. An archived key can be reactivated later if you change your mind before creating a replacement.
How it authenticates
A request carrying the X-API-Key header authenticates as the organization that created the
key, resolved server-side against the stored key record — there is no separate login step for
API-key requests. The same header also authenticates the MCP server surface, so one key covers
both the REST API and MCP access.
What it can reach
A key carries the same organization-level access as the user who created it — it is not scoped down to a subset of routes or resources by default. Treat a key as equivalent to that user's access for anything done through the API.
An API key carries your organization's access. Store it in a secret manager, never in source control, and rotate it if it may have been exposed.
Key hygiene
Archive a key the moment you stop using it rather than leaving it active indefinitely. Give each key a name that identifies where it's used — which server or script holds it — so an old key can be traced back to what depended on it before you archive it.
Common questions
What is Woise?
Woise is a managed platform for voice AI agents. You design an agent in a drag-and-drop workflow editor, connect a phone number, and it handles real inbound and outbound calls over the phone network or in the browser. The infrastructure, carrier setup and scaling are run for you.
Do I need a phone number to start?
You bring a number you already own and import it — that is the primary path today, and it means you keep your carrier relationship and your existing number. Agents can also take and place calls in the browser over WebRTC with no number at all.
How does billing work?
You are billed for the call minutes your agents actually use, metered as credits against your account. There is no seat licence and no per-agent fee, so an agent that takes no calls costs nothing to keep.
Can an agent connect to my CRM or calendar?
Yes. Agents can read from and write to your CRM, calendar and support tools through the integrations marketplace — you authorise each connection once with OAuth, and no credentials are stored in your workflow.
Do I need engineers to build an agent?
The workflow editor is visual, so building and changing an agent needs no code. There is also a REST API, a Python SDK and a TypeScript SDK if you would rather drive the platform programmatically, and an MCP server so coding agents can build workflows for you.
What happens to call recordings and transcripts?
Recordings and transcripts belong to your workspace and are available through the dashboard and the API. Raw transcripts, recordings and phone numbers are never handed to third-party analytics or error tracking without redaction.
What infrastructure do I have to run?
None. Woise runs the speech models, the language model turn, the call recording pipeline and the telephony legs for you, and scales them with your call volume. There is nothing to provision, patch or keep running.
Still stuck? Talk to our team.