Integrations & data access Client Intelligence API

Your customer intelligence, in the tools your team already uses.

Every Customer Conversations program includes read access to the intelligence behind your portal: published synthesis, campaigns, and quality-gated interviews. Pull it into a dashboard, hand it to an AI agent, or let a partner build on it, with a key you control.

OpenAPI spec Read the agent guide

What you can pull

The same numbers and documents your portal shows. Counts reconcile because the API applies the same usable-interview rules.

Published synthesis
The same quality-gated intelligence your team reads in the portal: home, lane, campaign, playbook, and creative-concept documents.
Campaigns
Your active research questions, briefs, and target segments, so downstream analysis can be scoped the way the program is run.
Interviews & analytics
Reportable interview metadata and the portal-parity volume, campaign, and sentiment series. Full transcripts only with an elevated scope.
Intelligence search
Search across structured extraction: competitor mentions, product feedback, pain points, and feature requests.

Three ways in

REST

Bearer-key JSON endpoints with keyset cursor pagination. updated_since on campaigns and synthesis for incremental syncs.

curl https://app.customerconversations.co/api/client/v1/synthesis \
  -H "Authorization: Bearer cc_..."

MCP

A Streamable HTTP MCP server for Claude Code and other agents. Same key, same scopes, same five readers exposed as tools.

{
  "mcpServers": {
    "customer-conversations": {
      "type": "http",
      "url": "https://app.customerconversations.co/api/client/v1/mcp",
      "headers": { "Authorization": "Bearer cc_..." }
    }
  }
}

BI tools

Pull the reportable corpus into Looker, Power BI, Google Sheets, or your warehouse on a schedule. The BI guide walks through it.

Open the BI guide

Documentation

Three documents, all public, all served from the API itself.

Base URL

https://app.customerconversations.co/api/client/v1

Getting a key

Keys belong to the brand, not to us. A client issues them from their own portal and decides who holds them and what they can see.

  1. 01

    Sign in to your portal

    app.customerconversations.co, any admin on your brand.

  2. 02

    Open the Developer page

    Issue a key, name it for who will hold it, and pick its scopes.

  3. 03

    Hand it to your team or partner

    Keys are brand-scoped: every response is already filtered to your data. Rotate or revoke any time.

Building on behalf of a client? Ask them to issue the key. It keeps the data-sharing decision with the brand and takes about a minute.

Good to know before you scope

Read-only
The API reads intelligence out. It does not start interviews, write segments, or change program settings.
No webhooks yet
Poll on a schedule. updated_since on campaigns and synthesis keeps incremental syncs cheap.
Scoped by default
Default keys return safe metadata and published intelligence. Transcripts, customer identity, and raw extraction each need an explicit elevated scope.
600 requests / hour
Per key, rolling window. Rate-limit headers on every response; 429s do not consume quota.
Docs match the code
The spec and guides are generated from the same definitions the API enforces, so they cannot drift from what is live.

Building an integration with a client on Customer Conversations?

Tell us what you're connecting and what would make it easier.

Talk to us