KaiCalls Concierge API
The Concierge API from KaiCalls — 2 operation(s) for concierge.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/kaicalls-com:kaicalls-com-concierge-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
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 Specification
openapi: 3.2.0
info:
title: KaiCalls Public Concierge API
version: '2026-06-05'
description: Machine-readable surface for KaiCalls external developers and client agents.
servers:
- url: https://www.kaicalls.com/api
security:
- bearerAuth: []
tags:
- name: Concierge
paths:
/v1/concierge/approval-email-receipts:
post:
summary: Receipt adapter for the configured outbound email worker (concierge:write)…
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- request_id
- business_id
properties:
request_id:
type: string
business_id:
type: string
provider_message_id:
type: string
provider_thread_id:
type: string
responses:
'200':
description: Receipt recorded
'400':
description: Missing/invalid request_id or business_id
'401':
description: Missing, invalid, revoked, or expired API key
'403':
description: Missing concierge:write scope, or no access to the business
'409':
description: Receipt rejected (e.g. unknown request_id)
x-required-scopes: concierge:write
tags:
- Concierge
operationId: postV1ConciergeApprovalEmailReceipts
x-operation-id-source: derived
/v1/concierge/approval-replies:
post:
summary: Optional inbound-email adapter (concierge:write) — records a customer reply…
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- request_id
- business_id
- from_email
- body
properties:
request_id:
type: string
business_id:
type: string
from_email:
type: string
format: email
body:
type: string
token:
type: string
message_id:
type: string
thread_id:
type: string
responses:
'200':
description: Reply recorded; decision is approve
'202':
description: Reply recorded; decision is not a clear approval
'400':
description: Missing/invalid request_id, business_id, from_email, or body
'401':
description: Missing, invalid, revoked, or expired API key
'403':
description: Missing concierge:write scope, or no access to the business
'409':
description: Reply rejected (e.g. unknown request_id)
x-required-scopes: concierge:write
tags:
- Concierge
operationId: postV1ConciergeApprovalReplies
x-operation-id-source: derived
components:
securitySchemes:
bearerAuth:
type: http
scheme: bearer
description: 'KaiCalls API key. Per-operation scope requirements are published on each operation as `x-required-scopes` — a scope string, or a nested `{ allOf: [...] }` / `{ anyOf: [...] }` expression. An operation with no `x-required-scopes` requires a valid key but no particular scope.'
x-scopes:
- workspaces:read
- workspaces:write
- numbers:read
- numbers:write
- agents:read
- agents:write
- communication-runs:read
- communication-runs:write
- calls:read
- calls:write
- sms:read
- sms:write
- webhooks:read
- webhooks:write
- events:read
- events:replay
- lifecycle:write
- leads:read
- leads:write
- emails:read
- emails:write
- sdr:read
- sdr:write
- evals:read
- evals:write
- appointments:read
- appointments:write
- knowledge:read
- knowledge:write
- products:read
- products:write
- integrations:write
- approvals:write
- concierge:write
- billing:read
- billing:write
- call_evidence:read
- call_evidence:write
- support:write
sessionAuth:
type: apiKey
in: cookie
name: sb-access-token
description: Authenticated dashboard session cookie. Used by first-party flows that mint or manage API keys.