Skip to main content
The Fluent API is served from:
All requests require a Fluent credential. See Authentication for supported headers and OAuth scopes.

​
Response format

Most successful JSON responses use a data envelope:
The connection discovery endpoints return their arrays directly for backwards compatibility. MCP endpoints use the Model Context Protocol’s Streamable HTTP response format. Errors are not wrapped:

​
Discovery

GET /api/v1 needs no credential. It returns the base URL, the supported authentication methods and OAuth scopes, the rate-limit and deprecation conventions, and links to these docs and the specification — enough for a client to find its way in before it has a key:

​
Compatibility

/api/v1 is a public compatibility boundary. New fields may be added to response objects. Clients should ignore fields they do not recognize and should not infer undocumented database structure from flexible record or document payloads. See Versioning and deprecation for what can change and how a removal is announced.

​
OpenAPI

Use the Download API spec action in the page header, or fetch the OpenAPI 3.1 specification from either of these stable URLs: