Skip to main content

​
API Keys

All API requests require a Bearer token sent in the Authorization header. Generate keys from the Ruune Dashboard under Settings → API Keys.
Request Header
Authorization: Bearer ruune_sk_live_xxxxxxxxxxxxx

​
Key Types

PrefixDescription
ruune_sk_live_Production key — full access to your account data.
ruune_sk_test_Test key — returns mock data, no real recordings affected.
Never expose API keys in client-side code, public repos, or browser requests. Use server-side calls or a backend proxy.

​
Example Request

cURL
curl https://api.ruune.ai/v1/notes \
  -H "Authorization: Bearer ruune_sk_live_xxxxxxxxxxxxx" \
  -H "Content-Type: application/json"

​
Scopes

By default, keys have full access. You can restrict keys to specific scopes when creating them:
ScopeDescription
notes:readRead notes, transcripts, highlights
notes:writeCreate, update, delete notes
recordings:readList and download recordings
searchSemantic search across all context
actions:readList action items
actions:writeUpdate action item status
webhooks:manageCreate, list, delete webhooks

​
MCP Authentication

The MCP server uses the same API key. Pass it as a header in your MCP client configuration:
MCP Config
{
  "mcpServers": {
    "ruune": {
      "url": "https://mcp.ruune.ai",
      "headers": {
        "Authorization": "Bearer ruune_sk_live_xxxxxxxxxxxxx"
      }
    }
  }
}