FluxDesk
← All integrations

Integrations · Push events in

Inbound API

Push events into a specific employee's FluxDesk inbox. Bearer-token auth — one token per direction, owned by one user.

Pick your mode

  • Mode 1 · Personal direct (recommended). Employee self-claims a flux-in-pers-… token from /me/agent. Configure once in your script / monitor / SaaS webhook and you're done.
  • Mode 2 · Admin moderation. Third-party systems push to a moderation token; admin reviews each event and forwards (or drops) to the right recipient. Best for unpredictable upstream content.
  • Mode 3 · Tools-claim. Admin issues a single flux-tools-… token; your CLI calls POST /api/v1/tokens/claim to mint per-employee personal tokens on demand. fd1 uses this to fan out onboarding events without managing N tokens.

Push one event (Mode 1)

The token's owner becomes the recipient — no recipient_hint needed. event_typemust carry the bearer's integrator prefix (e.g. monitoring.*).

shell
curl -X POST https://my.fluxdesk.net/api/v1/events \
  -H "Authorization: Bearer flux-in-pers-EXAMPLE…" \
  -H "Content-Type: application/json" \
  -d '{
    "event_type": "monitoring.disk_full",
    "title": "Disk 92% full on web-2",
    "body": "rotate logs or extend EBS",
    "tone": "negative"
  }'

Claim a personal token (Mode 3)

The employee must already have an approved team-support request against the catalog row linked to this tools-token. Replay-safe (same email → same token until rotated).

shell
curl -X POST https://my.fluxdesk.net/api/v1/tokens/claim \
  -H "Authorization: Bearer flux-tools-EXAMPLE…" \
  -H "Content-Type: application/json" \
  -d '{"email": "[email protected]"}'

Full spec & SDK