Build on the platformthat talks to your customers

A REST API, webhooks and an MCP server over the same Boom your team uses every day. Push your customer data in, hear about every conversation, and let your AI tools do the rest.

NewPeople API updates now merge
  • Bitso
  • Grupalia
  • Contalink
  • Solvento
  • Digitt
  • Vitau
  • Mattilda
  • Kontempo
  • Wallbit
  • Terapify
  • Nexu
  • Kroni
  • AnswerThis
  • Dogelthy
  • Treo
  • Commons
  • VitalBotanics
  • Sleep Rituals
  • Sleepy Bear Studio
  • Mubson
  • Bustin Boards

Everything in Boom has an API. The platform your team runs from the dashboard is open to your code, your data and the AI tools you already work in.

01REST API and keys

One key. Every object in Boom.

Create a key in Settings and work with every object in Boom: upsert people, record events, build segments, enroll participants in initiatives and publish journeys. Records are keyed by your own ids, so there is nothing to map.

Read the API docs
02Webhooks

Know when it happens, not when you poll.

Point a destination at your endpoint and Boom posts each event as it happens: a journey run starts or ends, an enrollment is rejected, a conversation is escalated to your team. Every delivery carries your stored credential and an Idempotency-Key, and failures are retried up to four attempts.

Read the webhooks docs
03MCP server

Boom, inside the AI tools you already use.

Add one URL to Claude, Cursor or VS Code and sign in with your Boom login. There is no key to copy: every tool follows your role, so your assistant can query customers, build segments, draft journeys and read results with exactly the access you have.

Connect the MCP server
  • Claude
  • Cursor
  • VS Code
  • GitHub Copilot
  • ChatGPT
  • Windsurf
  • Zed
Explore MCP docs
04Sidekick

Describe it. Sidekick builds it.

Sidekick is the agent inside Boom. Ask it to find conversations, size an audience from a sentence or a SQL query, or draft a whole journey, and it proposes the change on a card. Nothing runs until you approve it, and it acts with your permissions, never more.

See Sidekick in a demo
05Your tools

Your systems, in every conversation.

Give the agent a tool that calls your own endpoint, like an order lookup or an account status, and it calls it when a customer asks. You choose exactly which response fields it may read, and authentication lives in an encrypted credential the agent never sees.

Read about agent tools
And the rest

Everything else you can build on.

  • Claude

    Skills for Claude

    Install them with npx @useboom/skills-setup and Claude knows how to launch, design and analyze on Boom.

  • <script>

    Web widget

    One script tag puts the agent on your site, with Boom('open') and Boom('send') to drive it.

  • Forms

    Embedded forms

    Drop a form on any page and listen for boom:form-submitted on yours.

  • Postgres

    Connect your database

    A read-only user and a SELECT you write. Boom syncs it about every 15 minutes.

  • Events

    Transactional sends

    Post one event and Boom sends the message it triggers, once per event.

  • Privacy

    Sensitive fields

    Mark a field sensitive and every AI surface reads [redacted] in its place.

  • Limits

    Rate limits and errors

    1,000 requests a minute per key, one error shape and an X-Request-Id on every response.

  • Sandbox

    Development host

    Build against dev.useboom.ai with its own keys before you point at production.

Start building on Boom.

Create an API key in Settings, connect the MCP server with your Boom login, and send your first event in minutes.