API reference

Two families: the public API (chat, sessions, OTP) called from your site or server, and the admin API (JWT) to manage your workspace. All routes are prefixed with /api/v1.

• Chat: POST /re-act-agent/chat and POST /re-act-agent/chat/stream (SSE). Idempotency-Key header to retry without duplicates.
• Sessions: POST /re-act-agent/session/init, GET /re-act-agent/session/history, POST /re-act-agent/session/otp/request then /otp/verify.
• Admin: POST /admin/auth/login returns an accessToken, to send as Authorization: Bearer <token>.
• Resources: /admin/bots, /admin/functions (+ /:id/test), /admin/mcp/servers, /admin/connectors, /admin/webhooks (+ /:id/test), /admin/evals, /admin/guardrails/:botId, /admin/conversations, /admin/stats.
• Codes: 400 invalid request, 401 missing token or invalid signature, 403 insufficient role, 404 unknown resource, 409 conflict (message in progress, flow changed elsewhere), 429 rate limit.

# 1. Connexion : renvoie un accessToken
curl -X POST https://api.votredomaine.com/api/v1/admin/auth/login \
  -H "Content-Type: application/json" \
  -d '{ "email": "vous@entreprise.com", "password": "••••••••" }'

# 2. Appels d'administration
curl https://api.votredomaine.com/api/v1/admin/bots -H "Authorization: Bearer <accessToken>"