Build on Kustomer

What you can build on the Kustomer platform, how the pieces fit together, and where to start.

Kustomer is a customer service platform built around a single timeline per customer: every conversation, message, order and event lands on one record. The developer platform exposes that same data model through a REST API, real-time events, an apps platform and embeddable chat SDKs.

This site covers all of it, for engineers and for the AI tools they work with. Every page has a Markdown version, the whole site is summarized in /llms.txt, and every API operation has its own Markdown page in the API reference.

What you can build

How the platform fits together

Kustomer

Your systems

HTTPS + API key

kusty / MCP

Chat SDKs

Outbound webhooks

REST actions

Klasses, KViews, workflows

Backend services

Website and mobile apps

AI agents and scripts

REST API

Event stream

Workflows

Installed apps

Chat

Diagram source
flowchart LR
  subgraph You["Your systems"]
    S[Backend services]
    W[Website and mobile apps]
    A[AI agents and scripts]
  end
  subgraph K["Kustomer"]
    API[REST API]
    EV[Event stream]
    WF[Workflows]
    AP[Installed apps]
    CH[Chat]
  end
  S -- "HTTPS + API key" --> API
  A -- "kusty / MCP" --> API
  W -- "Chat SDKs" --> CH
  API --> EV
  CH --> EV
  EV --> WF
  EV -- "Outbound webhooks" --> S
  WF -- "REST actions" --> S
  AP -. "Klasses, KViews, workflows" .-> K
  • REST API. Everything an agent can see or do is a resource: customers, conversations, messages, custom objects, users, queues, knowledge base articles and settings. Base URL https://<your-org>.api.kustomerapp.com.
  • Events. Every create and update emits an event named kustomer.<object>.<action>. Workflows consume them inside Kustomer, and outbound webhooks deliver them to you.
  • Apps. An app definition is a JSON document that bundles Klasses (custom object types), KViews (UI views), workflows, settings and webhooks so you can install them into any org.
  • Chat SDKs. Native and web SDKs that put Kustomer Chat inside your product and identify signed-in customers.

Start here

  1. Create an API key

    In Kustomer, go to Settings › Security › API Keys and add a key with the roles your integration needs. See API keys and roles.

  2. Make your first call

    Follow the quickstart to read your org, create a customer and open a conversation in about five minutes.

  3. Learn the data model

    Read Data model overview to see how customers, conversations, messages and custom objects relate.

  4. Pick a guide

    Jump to a guide for the integration you're building, or browse the API reference.