Customer Alliance Insights API
AI recommendations, mentions and topics.
AI recommendations, mentions and topics.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/customer-alliance:customer-alliance-insights-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Customer Alliance Insights API
summary: Review management, surveys & feedback for hospitality — as an API.
version: 4.2.0
description: 'The Customer Alliance API gives you programmatic access to your reviews, surveys, analytics and AI insights, lets you push guests, reviews and survey responses in from your other systems, and lets you subscribe to events via outbound webhooks. ## Getting started
1. In the dashboard, go to **Settings → API** and create a key, granting only the scopes you need. 2. Copy the key (`ca_live_…`) — it''s shown once. 3. Send it as a Bearer token on every request:
```bash
curl https://app.customer-alliance.com/api/v4/reviews \
-H "Authorization: Bearer ca_live_your_key_here"
```
Call `GET /whoami` to confirm the key resolves to the account, node and scopes you expect. ## Authentication
Every request needs `Authorization: Bearer `. Keys are created and scoped in **Settings → API**. ## Scopes
Each key holds a subset of `reviews:read`, `surveys:read`, `analytics:read`, `insights:read`, `nodes:read`, `webhooks:manage`, `guests:write`, `reviews:write`, `surveys:write`. A call missing its scope returns `403`. ## Hierarchy
A key is bound to one node in your account hierarchy; **read** endpoints cover that node and its subtree, and **write** endpoints (`POST /guests`, `POST /reviews`, `POST /survey-responses`) write to one property within it. The webhook-management endpoints (`/webhooks*`) are the exception — they operate account-wide and ignore the key''s node binding (see **Webhooks**) — and so are the attribute definitions of `GET /property-attributes`, which describe the account rather than a property (see **Property attributes**). ## Display scope
By default, read endpoints return everything on your account''s subtree. An API key authenticates the account owner reading their own data — the same data the dashboard shows — so nothing is withheld from you. If the response will be shown to the public, pass `?display=public`:
```bash
curl "https://app.customer-alliance.com/api/v4/reviews?display=public" \
-H "Authorization: Bearer ca_live_your_key_here"
```
Supported on `GET /reviews` and `GET /reviews/{id}` (`reviews:read`), and `GET /insights/mentions` (`insights:read`). It excludes two groups: review portals whose content may not be republished (some license redisplay as a paid product, or have terms that have not been cleared for it), and sources whose authorship was never verified — reviews entered by hand (`manual`) and imported ones (`upload`: CSV uploads, and everything pushed through `POST /reviews` or `POST /survey-responses`). Only the exact value `public` opts in. Any other value is ignored and you get the default, unfiltered behaviour — deliberately, so that a typo cannot silently withhold data. Rather than tracking which platforms may be republished yourself, use `?display=public` and let the API apply the current set. > **Upgrading an existing integration.** `GET /reviews` previously withheld these platforms from every caller. It no longer does. If you use it to power anything the public sees, add `?display=public` before upgrading — without it you will begin receiving reviews from platforms that may not be republished. If you use it for internal analytics, reporting or warehousing, you need to do nothing; you simply get more complete data. ### Survey responses
Responses to your Customer Alliance surveys are never returned by `GET /reviews`, `GET /reviews/{id}` or `GET /insights/mentions`, with or without `display=public`. This is not a publishing restriction: a survey-bridged review is a representation of a response that `GET /surveys/{id}/responses` already serves, and returning it from both would make a consumer summing across them count the same feedback twice. To work with survey feedback, use the surveys endpoints. Survey responses imported from another tool — pushed through `POST /survey-responses` or uploaded as a CSV — are the reverse: they are returned by the review endpoints as `upload` reviews, and the surveys endpoints do not list them. Either way, each response is served exactly once.'
termsOfService: https://www.customer-alliance.com/en/terms-and-conditions/
contact:
name: Customer Alliance Support
email: info@customer-alliance.com
url: https://www.customer-alliance.com/
servers:
- url: https://app.customer-alliance.com/api/v4
description: Production
security:
- bearerAuth: []
tags:
- name: Insights
description: AI recommendations, mentions and topics.
paths:
/insights/recommendations:
get:
summary: List AI recommendations for the account (newest first)
description: Requires `insights:read`.
operationId: listRecommendations
tags:
- Insights
parameters:
- $ref: '#/components/parameters/cursor'
- $ref: '#/components/parameters/limit'
responses:
'200':
description: A page of recommendations.
content:
application/json:
schema:
type: object
required:
- data
- next_cursor
- has_more
properties:
data:
type: array
items:
$ref: '#/components/schemas/Recommendation'
next_cursor:
type:
- string
- 'null'
description: Pass as `?cursor=` to fetch the next page; null on the last page.
has_more:
type: boolean
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
/insights/mentions:
get:
summary: List topic mentions extracted from reviews in the key's subtree (newest first)
description: 'Requires `insights:read`. Returns mentions from every review on your account''s subtree by default — a mention is a snippet of a review you can already read, so the scope matches `GET /reviews`. If you are rendering mentions to the public, pass `?display=public`.
**Mentions from responses to your Customer Alliance surveys are never returned here**, with or without `display=public`, for the same reason as `GET /reviews`: the response is already served by `GET /surveys/{id}/responses`.'
operationId: listMentions
tags:
- Insights
parameters:
- $ref: '#/components/parameters/cursor'
- $ref: '#/components/parameters/limit'
- $ref: '#/components/parameters/display'
responses:
'200':
description: A page of mentions.
content:
application/json:
schema:
type: object
required:
- data
- next_cursor
- has_more
properties:
data:
type: array
items:
$ref: '#/components/schemas/Mention'
next_cursor:
type:
- string
- 'null'
description: Pass as `?cursor=` to fetch the next page; null on the last page.
has_more:
type: boolean
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
/insights/topics:
get:
summary: List the canonical topic labels readable by the account
description: Requires `insights:read`.
operationId: listTopics
tags:
- Insights
responses:
'200':
description: OK
content:
application/json:
schema:
type: object
required:
- data
properties:
data:
type: array
items:
$ref: '#/components/schemas/Topic'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
components:
schemas:
Mention:
type: object
description: A topic mention extracted from a review. `is_hidden` mirrors the source review's flag.
properties:
id:
type: string
format: uuid
review_id:
type: string
format: uuid
source_field:
type: string
example: text
text:
type: string
sentiment:
type:
- string
- 'null'
canonical_label_id:
type: string
format: uuid
custom_category_id:
type:
- string
- 'null'
format: uuid
confidence:
type:
- number
- 'null'
is_hidden:
type: boolean
created_at:
type: string
format: date-time
Recommendation:
type: object
properties:
id:
type: string
format: uuid
title:
type: string
body:
type: string
priority:
type: string
example: high
impact:
type:
- string
- 'null'
canonical_label_id:
type:
- string
- 'null'
format: uuid
created_at:
type: string
format: date-time
Error:
type: object
required:
- error
properties:
error:
type: string
example:
error: Invalid API key
Topic:
type: object
properties:
id:
type: string
format: uuid
name:
type: string
language:
type:
- string
- 'null'
parent_label_id:
type:
- string
- 'null'
format: uuid
responses:
Unauthorized:
description: Missing or invalid API key.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
Forbidden:
description: The key lacks the required scope, or the account's plan does not include it.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
parameters:
limit:
name: limit
in: query
schema:
type: integer
minimum: 1
maximum: 100
default: 25
display:
name: display
in: query
schema:
type: string
enum:
- public
description: 'Pass `public` when the response will be shown to the public — a custom widget, an embed, anything a site visitor reads. It excludes two groups of reviews:
- **Portals whose content may not be republished.** Some review portals license redisplay of their content as a paid product, or have terms that have not been cleared for it. Those reviews are yours to read, analyse and act on, but not to republish.
- **Sources whose authorship was never verified** — reviews entered by hand (`manual`) and imported ones (`upload`: CSV uploads, and everything pushed through `POST /reviews` or `POST /survey-responses`). Legitimate internal signal, but nobody confirmed a guest wrote them.
Only the exact value `public` opts in. Any other value is ignored and you get the default, unfiltered behaviour — a typo must not silently withhold data.
Omit it — the default — to read everything on your account. Responses to your Customer Alliance surveys are never served by these endpoints either way; see `GET /surveys/{id}/responses`.'
cursor:
name: cursor
in: query
schema:
type: string
description: Opaque pagination cursor from a prior response's next_cursor.
securitySchemes:
bearerAuth:
type: http
scheme: bearer
description: An API key created in Settings → API (`ca_live_…`).
externalDocs:
description: Customer Alliance
url: https://www.customer-alliance.com/