Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 03:37 UTC
| 1 | These endpoints handle files that tools read and write during execution. When a tool produces or consumes a file, Composio stores it in object storage and exchanges it through presigned URLs rather than streaming bytes through the API. |
| 2 | |
| 3 | You reach for these endpoints to: |
| 4 | |
| 5 | - **List files** that tools have generated, optionally filtered by app and action. |
| 6 | - **Request an upload**: get a presigned S3 URL, `PUT` your file to it, then pass the returned reference into a tool's input. |
| 7 | |
| 8 | This keeps large payloads out of request bodies. Tools receive a file reference and resolve the underlying object on their side. |
| 9 | |
| 10 | <Callout type="info"> |
| 11 | File uploads are a two-step flow. Call the upload-request endpoint to mint a presigned URL, then upload the file contents directly to that URL. The API never receives the raw bytes. |
| 12 | </Callout> |
| 13 | |
| 14 | If your agent works with files inside a session, prefer the session file mount, where the sandbox exposes uploaded files to running code. See the [remote sandbox](/docs/sandbox/remote) for the sandbox helpers (`upload_local_file`, `smart_file_extract`) that build on this storage. |
| 15 | |
| 16 | These endpoints use your project API key in the `x-api-key` header. |