Otter.ai Public API (beta)

Enterprise plan users are currently limited to 10 requests / second. If you exceed your rate limit, you'll receive a 429 Too Many Requests response.

List endpoints use cursor-based pagination for efficient data retrieval.

Pagination Response

{
  "meta": {
    "retrieved_at": "2025-07-31T12:00:00Z",
    "has_more": true,
    "next_cursor": "next_cursor_position"
  },
  "data": [ /* array of results */ ]
}

Meta Fields

Usage

To retrieve the next page, use the next_cursor value in your next request's cursor query parameter:

GET /conversations?cursor=next_cursor_position&limit=20

Continue paginating until has_more is false.

A Channel lets you organize Conversations.

{
  "id": "channel_id",
  "name": "Backend Weekly Meeting",
  "member_count": 50,
  "owner": {
    "id": "user_id",
    "name": "Jane Doe",
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "jane@test.com"
  }
}

GET /channels

Returns a cursor-paginated list of channels that the authenticated user is in, ordered alphabetically by channel name.

Query Parameters:

Example Request:

curl -X GET "<https://api.otter.ai/v1/channels?limit=20>" \\
  -H "Authorization: Bearer YOUR_API_KEY"

Response: Returns a ChannelListResponse with channel data and pagination metadata.

{
  "meta": {
    "retrieved_at": "2025-07-31T12:00:00Z",
    "has_more": true,
    "next_cursor": "next_cursor_position"
  },
  "data": [
    {
      "id": "channel_id",
      "name": "Backend Weekly Sync",
      "member_count": 50,
      "owner": {
        "id": "user_id",
        "name": "Jane Doe",
        "first_name": "Jane",
        "last_name": "Doe",
        "email": "Jane@test.com"
      }
    }
  ]
}

• POST /conversations
• GET /conversations
• GET /conversations/{id}

POST /conversations

Creates a new conversation from a file. This is useful if you are importing calls into Otter, such as from a Dialer.

Request Body:

Example Request:

curl -X POST "<https://api.otter.com/v1/conversations>" \\
  -H "Authorization: Bearer YOUR_API_KEY" \\
  -H "Content-Type: application/json" \\
  -d '{
    "file": "<https://example.com/file.mp4>",
    "name": "Product Launch Meeting"
  }'

Response: Returns a ConversationCreateResponse with status.

{
 "status": "success",
 "completed_at": "2025-12-01 01:00:00Z",
 "file": "audio.mp3"
}

GET /conversations

Returns a cursor-paginated list of conversations, ordered by creation time (most recent first).

Query Parameters:

Example Request:

curl -X GET "<https://api.otter.ai/v1/conversations?limit=50&include_shared=true>" \\
  -H "Authorization: Bearer YOUR_API_KEY"

Response: Returns a ConversationListResponse with conversation data and pagination metadata.

{
  "meta": {
    "retrieved_at": "2025-10-05T12:34:56.789012Z",
    "has_more": true,
    "next_cursor": "cursor_id"
  },
  "data": [
    {
      "id": "conversation_id",
      "title": "Team Sync – Weekly Planning",
      "url": "<https://otter.ai/u/conversation_id>",
      "owner": {
        "id": "owner_id",
        "name": "Jane Doe",
        "first_name": "Jane",
        "last_name": "Doe",
        "email": "jane.doe@example.com"
      },
      "created_at": "2025-10-05T12:33:10Z",
      "process_status": {
        "abstract_summary": "completed",
        "action_item": "completed",
        "outline": "completed"
      },
      "calendar_guests": [
        {
          "name": "John Smith",
          "email": "john.smith@example.com",
          "permission": "view"
        }
      ],
      "shared_emails": [
        {
          "email": "guest.user@example.com",
          "user": {
            "id": "user_id",
            "name": "Guest User",
            "first_name": "Guest",
            "last_name": "User",
            "email": "guest.user@example.com"
          },
          "permission": "collaborate"
        }
      ],
      "shared_channels": [
        {
          "channel": {
            "id": "channel_id",
            "name": "Project Alpha",
            "member_count": 12,
            "owner": {
              "id": "owner_id",
              "name": "Alex Johnson",
              "first_name": "Alex",
              "last_name": "Johnson",
              "email": "alex.johnson@example.com"
            }
          },
          "permission": "view"
        }
      ],
      "abstract_summary": "This is the summary.",
      "conf_join_url": "<https://zoom.us/j/00000000000>"
    }
  ]
}

GET /conversations/{id}

Returns the summary and details of a specific conversation, optionally including additional data - action items, insights, outline, transcript, or all.

Query Parameters:

Options: action_items, insights, outlines, transcript, all. If all is specified, every field will be returned. Example: insights,transcript |

Example Request:

curl -X GET "<https://api.otter.ai/v1/conversations/conversation_id?include=insights,transcript>" \\
  -H "Authorization: Bearer YOUR_API_KEY"

• Response: Returns a ConversationResponse with conversation details and requested relationships.

  {
    "meta": {
      "retrieved_at": "2025-10-05T12:00:00Z"
    },
    "data": {
      "id": "conversation_id",
      "title": "Customer Discovery Call – ACME Corp",
      "url": "<https://otter.ai/u/conversation_id>",
      "owner": {
        "id": "owner_id",
        "name": "Jane Doe",
        "first_name": "Jane",
        "last_name": "Doe",
        "email": "jane.doe@example.com"
      },
      "created_at": "2025-10-05T11:55:00Z",
      "process_status": {
        "abstract_summary": "finished",
        "action_item": "finished",
        "outline": "finished"
      },
      "calendar_guests": null,
      "shared_emails": [],
      "shared_channels": [
        {
          "channel": {
            "id": "channel_id",
            "name": "All customer calls",
            "member_count": 25,
            "owner": {
              "id": "channel_owner_id",
              "name": "John Smith",
              "first_name": "John",
              "last_name": "Smith",
              "email": "john.smith@example.com"
            }
          },
          "permission": "collaborate"
        }
      ],
      "abstract_summary": "The team met with ACME Corp to confirm their requirements, discuss pricing options, and align on an evaluation timeline for adopting Otter.ai across their go-to-market team.",
      "conf_join_url": "<https://zoom.us/j/00000000000>",
      "relationships": {
        "insights": [
          {
            "topic": "Budget",
            "text": [
              "ACME has a preliminary budget in place and is comfortable with a per-seat model as long as usage is clear.",
              "They are open to a flat-rate option if it simplifies internal approvals."
            ]
          },
          {
            "topic": "Authority",
            "text": [
              "Alex Taylor is the main champion, but final approval will come from the VP of Operations.",
              "Security and procurement teams will review the proposal before signature."
            ]
          },
          {
            "topic": "Need",
            "text": [
              "ACME needs automated call summaries for customer meetings and better visibility into team activity.",
              "They want to reduce manual note-taking and ensure consistent follow-up on action items."
            ]
          },
          {
            "topic": "Timeline",
            "text": [
              "They aim to complete evaluation this month and go live at the start of next quarter.",
              "Next internal decision checkpoint is scheduled for next week."
            ]
          }
        ],
        "transcript": {
          "content": "Jane Doe  00:00\\nThanks everyone for joining today. I’d love to understand how your team handles customer calls and where Otter might help.\\n\\nAlex Taylor  00:07\\nRight now we take notes manually, and we often miss details or lose track of follow-ups after the meeting.\\n\\nJane Doe  00:14\\nThat makes sense. Otter can automatically capture the conversation, generate summaries, and highlight key action items.\\n\\nAlex Taylor  00:21\\nThat would be really valuable for us, especially for onboarding new reps and improving consistency.\\n\\nJane Doe  00:28\\nGreat—I'll send a follow-up with pricing options and a proposed rollout timeline.\\n\\nAlex Taylor  00:35\\nSounds good. We'll review internally and get back to you this week.",
          "format": "txt"
        }
      }
    }
  }

Example Request:

curl -X GET "<https://api.otter.ai/v1/conversations/conversation_id?include=all>" \\
  -H "Authorization: Bearer YOUR_API_KEY"

• Response: Returns a ConversationResponse with conversation details and requested relationships.

  {
    "meta": {
      "retrieved_at": "2025-10-05T12:00:00Z"
    },
    "data": {
      "id": "conversation_id",
      "title": "Customer Discovery Call – ACME Corp",
      "url": "<https://otter.ai/u/conversation_id>",
      "owner": {
        "id": "owner_id",
        "name": "Jane Doe",
        "first_name": "Jane",
        "last_name": "Doe",
        "email": "jane.doe@example.com"
      },
      "created_at": "2025-10-05T11:55:00Z",
      "process_status": {
        "abstract_summary": "finished",
        "action_item": "finished",
        "outline": "finished"
      },
      "calendar_guests": null,
      "shared_emails": [],
      "shared_channels": [
        {
          "channel": {
            "id": "channel_id",
            "name": "All customer calls",
            "member_count": 25,
            "owner": {
              "id": "channel_owner_id",
              "name": "John Smith",
              "first_name": "John",
              "last_name": "Smith",
              "email": "john.smith@example.com"
            }
          },
          "permission": "collaborate"
        }
      ],
      "abstract_summary": "The team met with ACME Corp to confirm their requirements, discuss pricing options, and align on an evaluation timeline for adopting Otter.ai across their go-to-market team.",
      "conf_join_url": "<https://zoom.us/j/00000000000>",
      "relationships": {
        "action_items": [
          {
            "id": "action_item_id_1",
            "text": "Send follow-up email with pricing summary and implementation overview.",
            "assignee": {
              "id": "owner_id",
              "name": "Jane Doe",
              "first_name": "Jane",
              "last_name": "Doe",
              "email": "jane.doe@example.com"
            },
            "status": null
          },
          {
            "id": "action_item_id_2",
            "text": "ACME to confirm final user count and preferred contract term.",
            "assignee": {
              "id": "customer_contact_id",
              "name": "Alex Taylor",
              "first_name": "Alex",
              "last_name": "Taylor",
              "email": "alex.taylor@example.com"
            },
            "status": null
          }
        ],
        "insights": [
          {
            "topic": "Budget",
            "text": [
              "ACME has a preliminary budget in place and is comfortable with a per-seat model as long as usage is clear.",
              "They are open to a flat-rate option if it simplifies internal approvals."
            ]
          },
          {
            "topic": "Authority",
            "text": [
              "Alex Taylor is the main champion, but final approval will come from the VP of Operations.",
              "Security and procurement teams will review the proposal before signature."
            ]
          },
          {
            "topic": "Need",
            "text": [
              "ACME needs automated call summaries for customer meetings and better visibility into team activity.",
              "They want to reduce manual note-taking and ensure consistent follow-up on action items."
            ]
          },
          {
            "topic": "Timeline",
            "text": [
              "They aim to complete evaluation this month and go live at the start of next quarter.",
              "Next internal decision checkpoint is scheduled for next week."
            ]
          }
        ],
        "outlines": [
          {
            "section": "Introductions and Context",
            "text": [
              "Participants introduced themselves and clarified roles.",
              "ACME shared context on their current workflow and challenges with manual note-taking."
            ]
          },
          {
            "section": "Pricing and Rollout Options",
            "text": [
              "The team reviewed per-seat and flat-rate pricing options.",
              "They discussed rollout plans starting with key go-to-market teams and expanding later."
            ]
          }
        ],
        "transcript": {
          "content": "Jane Doe  00:00\\nThanks everyone for joining today. I’d love to understand how your team handles customer calls and where Otter might help.\\n\\nAlex Taylor  00:07\\nRight now we take notes manually, and we often miss details or lose track of follow-ups after the meeting.\\n\\nJane Doe  00:14\\nThat makes sense. Otter can automatically capture the conversation, generate summaries, and highlight key action items.\\n\\nAlex Taylor  00:21\\nThat would be really valuable for us, especially for onboarding new reps and improving consistency.\\n\\nJane Doe  00:28\\nGreat—I'll send a follow-up with pricing options and a proposed rollout timeline.\\n\\nAlex Taylor  00:35\\nSounds good. We'll review internally and get back to you this week.",
          "format": "txt"
        },
        "custom_prompt": null
      }
    }
  }