---
title: "REST API"
url: "https://raconte.ai/en/docs/api"
---

### Documentation

[Introduction](/en/docs)[Getting started](/en/docs/getting-started)[MCP server](/en/docs/mcp)[Webhooks](/en/docs/webhooks)[REST API](/en/docs/api)[CLI](/en/docs/cli)[SDK](/en/docs/sdk)[Agent skill](/en/docs/skill)

### Guides

[Configure the MCP server](/en/guides/mcp-setup)[Using the MCP server](/en/guides/mcp-usage)

[Raconte](/) ⟩ [Documentation](/en/docs)

# REST API

Manage interviews and invitations over HTTP with an organization API key.

Raconte exposes a REST API to manage **interviews** and **invitations** directly over HTTP. It is the same surface the [MCP server](/en/docs/mcp) drives, available to any HTTP client. Use MCP when you want an AI agent to operate the product, and the REST API when you integrate from your own backend. For terminals and scripts, reach for the [CLI](/en/docs/cli); for TypeScript or Node apps, the [SDK](/en/docs/sdk).

The complete, interactive reference (every endpoint, parameter, schema, and a built-in “try it”) lives here:

[Open the interactive API reference →](/en/docs/api-reference)

## Base URL

```
https://api.raconte.ai
```

Every path is prefixed with `/api`, for example `https://api.raconte.ai/api/interviews`.

## Authentication

Authentication uses an organization API key, created from [Settings → API](/settings/api) in the app and scoped to one organization. Every request runs against that organization; resources from other orgs are never returned.

Pass the key as a Bearer token:

```
Authorization: Bearer YOUR_API_KEY
```

An `x-api-key: YOUR_API_KEY` header is also accepted.

```
curl https://api.raconte.ai/api/interviews \
  -H "Authorization: Bearer YOUR_API_KEY"
```

## What you can do

*   **Interviews**: create, list, read, update, archive/restore, regenerate the intro or first message, and read activity logs.
*   **Invitations**: create (single or bulk), list, read, update, send, cancel, reactivate, archive/restore, read logs, and get a presigned audio URL for a message.

Account-level operations (billing, webhooks, API key management, organization settings) are **not** available through API keys: they stay in the authenticated app.

See the [interactive reference](/en/docs/api-reference) for the full request and response schemas.

Table of contents

[1\. Base URL](#base-url)[2\. Authentication](#authentication)[3\. What you can do](#what-you-can-do)