FruxonDocs
ApiParticipants

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.

POST
/v1/tenants/{tenant}/participants/{participant}:send
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

participant*string

The participant identifier.

Formatuuid
tenant*string

The tenant identifier

The smoke-test payload.

message*string|null

The text to dispatch.

providerOverride?string|null

Optional provider id (slack, telegram, …) to force the selector to prefer that channel. Falls back to the participant's normal priority order when null.

[key: string]?never

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"
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}