How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Chatbase

Chatbase Contacts API

Manage contacts and custom attributes for a chatbot.

Documentation Provider Profile APIs.io OpenAPI GitHub

Chatbase Contacts API is one of 5 APIs that Chatbase publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Contacts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 8 operations across 4 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://www.chatbase.co/api/v1.

8 operations 4 paths 5 schemas 1 DELETE3 GET1 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://www.chatbase.co/api/v1
Authentication
HTTP Bearer
Contact
Chatbase Support
Terms of Service
View terms
Resource Areas
1

Authentication & Security 1

Chatbase Contacts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer API key created in the Chatbase dashboard (Workspace Settings - API Keys).

Paths & Operations 8

Across 4 paths, the API surfaces 8 operations — 1 DELETE, 3 GET, 1 PATCH, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Contacts 8

Manage contacts and custom attributes for a chatbot.

POST
/chatbots/{chatbotId}/contacts
Create contacts
createContacts 1 param body → 200401
GET
/chatbots/{chatbotId}/contacts
List contacts
listContacts 3 params → 200401
GET
/chatbots/{chatbotId}/contacts/{contactId}
Get a contact
getContact 2 params → 200401
PATCH
/chatbots/{chatbotId}/contacts/{contactId}
Update a contact
updateContact 2 params body → 200401
DELETE
/chatbots/{chatbotId}/contacts/{contactId}
Delete a contact
deleteContact 2 params → 200401
POST
/chatbots/{chatbotId}/custom-attributes
Create a custom attribute
createCustomAttribute 1 param body → 200401
GET
/chatbots/{chatbotId}/custom-attributes
Get the custom-attribute schema
getCustomAttributes 1 param → 200401
PUT
/chatbots/{chatbotId}/custom-attributes/{name}
Update a custom attribute
updateCustomAttribute 2 params body → 200401

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are ContactInput (4 properties), Status (2 properties), Error (2 properties), CustomAttribute (2 properties). Each schema is shown below with its type and property counts.

Contact
CustomAttribute
object
2 properties 2 required
Error
object
2 properties
Status
object
2 properties
ContactInput
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

chatbase-contacts-api-openapi.yml Raw ↑

Other APIs Chatbase publishes across the network.

Chatbase Chat API
AE Profile APIs.io
Chatbase Chatbots API
AE Profile APIs.io
Chatbase Conversations API
AE Profile APIs.io
Chatbase Leads API
AE Profile APIs.io
#Contacts
← Back to C APIs
API Details
ID
chatbase:chatbase-contacts-api
Base URL
https://www.chatbase.co/api/v1
Docs
https://www.chatbase.co/docs/developer-guides/api-integration
Provider
Chatbase
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=chatbase-contacts-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/chatbase-contacts-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Chatbase Contacts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.