Qubit API v1

Business events

Start automations from your own system.

The business builds automations in the dashboard - "when an order is paid, send the thank-you template, tag the contact, create a follow-up in three days" - and your system fires the trigger. You send a named event; the platform runs whatever workflows listen for it.

Sending an event

Request
Try it - send it and see the response

This is a real request. A test key still acts on its workspace: a send goes out on the connection named in the body. Point it at your own number.

The answer is 202 with the event id and how many workflows were started. Zero is not an error; it means nothing listens for that name yet.

What runs

Only published workflows with an External API event trigger matching the name - Automations shows how the business builds one and what it can do. The business sees every run step by step in the dashboard - what fired, which conditions held, what each action did - and your request_id is on the run, so a "why did my customer get this?" question is answerable.

Idempotency

POST /events is a write, so the Idempotency-Key header is required like every other mutation (Idempotency). The key deduplicates the HTTP call for 24 hours; dedupe_key deduplicates the business event for as long as the subject exists. Use both.

Base URL https://communication-api.artofluminaire.com Every response carries X-Request-ID; quote it when you write to support.