Smoke-tests the outbound dispatch pipeline — picks a channel via the channel selector, decrypts the integration config, and routes through the per-provider sender (currently a logging stub for every provider — real senders land in Phase 3d.3)
Smoke-tests the outbound dispatch pipeline end to end: the channel selector picks a channel for the participant, the integration config is decrypted, and the message is handed to the per-provider sender. Use it to confirm a participant is reachable before relying on it in a flow. Returns 404 when the participant does not exist.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The participant identifier.
uuidThe tenant identifier
The smoke-test payload.
The text to dispatch.
Optional provider id (slack, telegram, …) to force the selector to prefer that channel. Falls back to the participant's normal priority order when null.
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/participants/497f6eca-6276-4993-bfeb-53cbbbba6f08:send" \ -H "Content-Type: application/json" \ -d '{ "message": "string" }'{
"outcome": "NO_CHANNEL"
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Creates a participant and optionally binds it to a set of agents atomically.
Creates the participant together with its channels and any initial agent bindings supplied in the request — all in one transaction, so a participant is never persisted half-bound. `Kind` is fixed at creation: switching a participant between Person, Group, and AI Agent requires recreating it.
Lists triggers in the tenant
Returns every trigger in the tenant with its current agent bindings. The two optional filters compose: `agentId` narrows to triggers bound to one agent, `integration` narrows to triggers sourced from one integration. The result is unpaged.