API Reference¶

The reference below is generated directly from AiFlow's own route definitions, the same schema every deployment computes from its running code, so it can't drift out of sync the way a hand-maintained reference could. It covers the complete surface documented on this site: Agents, context and knowledge, tools, Orchestrators, calls, triggers, team management, the audit log, API keys, webhook subscriptions, the widget, and observability. It excludes only Twilio's own inbound webhook endpoints, which Twilio calls directly and verifies with its own signature scheme, never a credential a client holds.

Making live test requests¶

Every AiFlow deployment also serves this same reference live, from its own running instance, at https://api.your-domain.com/docs. That version's Authorize button accepts either credential documented in Authentication, an admin session token for configuration endpoints or an API key for integration endpoints, and its Try it out button sends a real request against your own deployment and data, something the static copy embedded above can't do.

What's documented where¶

This site's guides are for learning the concepts and copying working examples in your language of choice. The reference above (or its live equivalent on your own deployment) is for exhaustive, field-by-field detail (exact optional fields, exact types, exact response shapes) for the moments a guide's prose doesn't spell out something you need.