Getting Started

Developer Overview

Pick the integration path that matches what you’re building. Embed gives you a drop-in widget; the REST API is for backends and custom UIs. Both are shipping today.

Two integration paths

The Chatmount platform exposes two surfaces for developers:

JavaScript Embed — drop a single async <script> on your site to render the chat widget. No build step, no client-side keys to manage
REST API — POST /v1/chat from a backend, serverless function, or any HTTP client. Useful for custom UIs, mobile apps, or pre-/post-processing prompts on your own infra

JavaScript embed

One script tag installs the widget. The chatbot ID is encoded in the URL path — no separate config object or data attribute required.

html

<script
  src="https://services.chatmount.co/embed/YOUR_CHATBOT_ID.js"
  async
></script>

Detailed setup: JavaScript Embed Script.

REST API

A focused HTTPS API. The v1 surface exposes the chat endpoint — send a message, get a response. Bearer-token auth with keys scoped to a single chatbot.

text

POST https://services.chatmount.co/v1/chat

Detailed setup: REST API Integration. Endpoint reference: Chat with a chatbot.

What ships today

A lot of the developer surface is documented here as a design spec — many features (programmatic widget control, event listeners, client-side actions/forms, custom domains, help-page proxy, contacts CRUD) are not live yet. Each page in the Developer Guide and API Reference flags its current state at the top with a callout.

JavaScript Embed Script

Drop the loader on your site and the widget mounts itself.

REST API Integration

Auth, base URL, error handling, rate limits.

Webhooks

Lead-capture webhooks — the one event we currently fire.