API reference index
Use these references for the supported workflows described in this manual. An application network request is not automatically a public integration contract.
| Interface | Reference | Authentication context |
|---|---|---|
| Project GraphQL | Generated schema | Project-authorized token or supported signed-in flow. |
| Assets | Upload and metadata | Authorized project request. |
| File delivery | Files | Original bytes, inline viewing, and downloads. |
| Image delivery | Images | Delivery URL; separate from Studio membership. |
| Studio search | Search hook | Signed-in Studio context. |
| Outgoing events | Webhooks | Receiver authentication configured in headers. |
| AI client connection | MCP | OAuth user authority. |
| Application tools | Tool contract | Signed server invocation. |
Manage chats, runs, approvals, skills, memberships, and integrations through the documented product workflows unless a separately supported API contract is provided for your integration. Do not build a production dependency on undocumented Dashboard session endpoints.
For client failures, distinguish transport status from GraphQL errors and business outcome. Include redacted request IDs and timestamps when seeking support.
Last updated on