wehub-resource-sync
17 lines
1.2 KiB
Plaintext
17 lines
1.2 KiB
Plaintext
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.
|
|
|
|
You reach for these endpoints to:
|
|
|
|
- **List files** that tools have generated, optionally filtered by app and action.
|
|
- **Request an upload**: get a presigned S3 URL, `PUT` your file to it, then pass the returned reference into a tool's input.
|
|
|
|
This keeps large payloads out of request bodies. Tools receive a file reference and resolve the underlying object on their side.
|
|
|
|
<Callout type="info">
|
|
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.
|
|
</Callout>
|
|
|
|
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.
|
|
|
|
These endpoints use your project API key in the `x-api-key` header.
|