Botcake API

Name: Botcake API API
Brand: Botcake API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsChat MessagingapiKey18 EndpointsREST

For Agents

Manage Botcake chatbot conversations, customer profiles, bots, and conversation analytics across 18 endpoints.

Quickstart

Get started with Botcake API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a Botcake chatbot message"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Botcake API API.

Create and update customer profiles with attributes used by chatbot flows

Deploy, update, and remove chatbots tied to a workspace

Send and read messages within an active conversation

Open new conversations and update conversation status or assignment

Pull conversation and message volume analytics for a date range

GET STARTED

Start building with Botcake API API

Explore with Jentic

View OpenAPI Document

Use for: Create a Botcake customer for a new website signup with their email and locale, Send a follow-up message to an existing conversation, List the bots configured in this Botcake workspace, Update a customer's attributes after they completed onboarding

Not supported: Does not handle SMS, email delivery, or voice calls — use for Botcake chatbot conversation, customer profile, and analytics management only.

Jentic publishes the only available OpenAPI document for Botcake API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Botcake API, keeping it validated and agent-ready. Botcake is a chatbot and customer engagement platform that lets brands run automated and live conversations with customers across messaging channels. The API exposes customers, bots, conversations, messages, and analytics so teams can sync customer profiles, deploy and update bots, send and receive messages, and report on conversation volumes. Authentication uses an X-API-Key header.

Use Cases

Patterns agents use Botcake API API for, with concrete tasks.

★ Customer profile sync into Botcake

Marketing and product teams keep Botcake customer profiles in sync with their main customer database so chatbot flows can personalise greetings and segment messages. The API accepts POST /customers for new records and PUT /customers/{customerId} for updates, with attributes that bots consume at runtime. Most teams build the sync as a webhook or nightly job in a couple of days.

Create a Botcake customer with email user@example.com, name 'Alex Kim', and attribute plan='pro', then return the new customer id

Outbound chatbot messaging

Support and lifecycle teams trigger outbound messages from Botcake when an external event happens (order shipped, ticket resolved, renewal upcoming). POST /conversations creates or fetches the active conversation, then POST /conversations/{conversationId}/messages sends the message body. Teams typically wire this into existing webhook pipelines within a sprint.

Open a conversation with customer cust_123 and send the message 'Your order has shipped, tracking number XYZ123'

Conversation analytics dashboards

Operations leaders want a daily view of conversation volume, response load, and busy windows. GET /analytics/conversations and GET /analytics/messages return time-series counts that feed BI tools or weekly reports. Dashboards usually go live in a day once authentication and date filtering are in place.

Pull GET /analytics/conversations for the last 7 days grouped by day and report the busiest day with its count

Agent-driven Botcake operations via Jentic

An AI agent monitors a queue of customer events and uses Botcake to message the right customer, update their profile, or resolve their conversation. Through Jentic the agent searches for 'send a Botcake message' or 'update a Botcake customer', loads the schema, and executes the call while the X-API-Key stays inside the Jentic vault.

Search Jentic for 'send a Botcake message', load the schema, and execute it for conversation conv_777 with the message 'Thanks for your patience, your refund is processed.'

Key Endpoints

18 endpoints — jentic publishes the only available openapi specification for botcake api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/customers

Create a customer profile

PUT

/customers/{customerId}

Update a customer profile

POST

/conversations

Open a new conversation

POST

/conversations/{conversationId}/messages

Send a message in a conversation

GET

/conversations/{conversationId}/messages

List messages in a conversation

POST

/bots

Create a bot

GET

/analytics/conversations

Conversation volume analytics

GET

/analytics/messages

Message volume analytics

POST

/customers

Create a customer profile

PUT

/customers/{customerId}

Update a customer profile

POST

/conversations

Open a new conversation

POST

/conversations/{conversationId}/messages

Send a message in a conversation

GET

/conversations/{conversationId}/messages

List messages in a conversation

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Botcake X-API-Key is stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution access only; the raw key never enters prompts, logs, or tool outputs.

Intent-based discovery

Agents search Jentic for intents like 'send a chatbot message' or 'update a Botcake customer' and Jentic returns the matching operations with their input schemas, so the agent picks the right endpoint without crawling docs.

Time to first call

Direct Botcake integration: 1-3 days for auth, customer sync, and analytics wiring. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Chatfuel API

No-code chatbot platform with a similar focus on Messenger and customer engagement.

Use Chatfuel when the team is already on its Messenger-focused builder; use Botcake when the workflows need its analytics and conversation primitives.

Alternative

Tidio API

Live chat and chatbot platform popular with e-commerce stores.

Choose Tidio when the priority is live chat agent handover on a storefront; choose Botcake when bot-led automation is the main channel.

Alternative

Intercom API

Customer messaging platform with deeper support and product-tour features.

Use Intercom for SaaS support and onboarding messaging; use Botcake for lighter-weight chatbot deployments with simpler analytics.

Complementary

ChatBot API

Bot-building platform that pairs with Botcake to author flows used in Botcake conversations.

Pair ChatBot for flow authoring with Botcake for runtime conversations and customer state.

FAQs

Specific to using Botcake API API through Jentic.

Why is there no official OpenAPI spec for Botcake API?

Botcake does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Botcake API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Botcake API use?

Botcake uses an API key passed in the X-API-Key request header. Issue the key from your Botcake workspace and store it in the Jentic vault so the raw key is never exposed to agents at execution time.

Can I send a chatbot message with the Botcake API?

Yes. POST /conversations to open or fetch an active conversation, then POST /conversations/{conversationId}/messages with the message body. The endpoint returns the created message id, which you can correlate with later analytics calls.

How do I update a customer's attributes through Jentic?

Run pip install jentic, then search Jentic for 'update a Botcake customer', load the PUT /customers/{customerId} schema, and execute it with the customer id and the attribute payload. Jentic injects the X-API-Key automatically.

What are the rate limits for the Botcake API?

Botcake does not document explicit per-second rate limits in the spec. For bulk customer syncs, batch updates and stagger requests; for analytics, query daily aggregates rather than minute-level windows to avoid unnecessary calls.

Can I pull conversation volume analytics?

Yes. GET /analytics/conversations and GET /analytics/messages return counts over a time range, suitable for daily and weekly reports. Pair them with conversation id lookups when you need to drill from a count down to specific transcripts.