Developers
Conceptual map of FlexyAgents APIs: authentication, agent chat, streaming, rate limits, and links to the platform API reference.
FlexyAgents exposes HTTPS endpoints for programmatic chat and related operations. Your deployment host determines base URLs—use the values from your environment, not hardcoded examples from generic docs.
For endpoint tables, request/response samples, and webhook shapes, use the marketing Platform → API page and your live OpenAPI spec if published.
Bearer tokens identify organizations and connections. Scope keys to the minimum agents required.
Prefer short-lived tokens or rotation policies where the product supports them.
POST-style chat endpoints accept messages and return model output; streaming variants emit incremental events suitable for SSE or NDJSON consumers.
Handle disconnects gracefully—resume UX should not duplicate side effects if your client retries.
Limits protect shared infrastructure; backoff with jitter when you receive 429s.
Log error bodies sparingly in production; they may contain user content.
Some knowledge upload endpoints return HTTP 402 when hosted monthly quotas for AI image description or media transcription are exhausted; error payloads may include a machine-readable code—handle these in your integration to prompt admins to add a Gemini key or raise plan limits.
Continue exploring
Platform features · HTTP API & webhooks · Quickstart · Contact
Build on your stack
Start a trial or talk to us about rollout, governance, and enterprise requirements.