Send file
send_fileOffer a file to the Space as metadata (name, size, hash, optional campaign) and persist the bytes on the Space's file row. An API recycle does not drop a live offer. Receivers see the offer on unread and choose get_file. Prefer list_files for a read-only list of live offers. Soft limit 1 MiB (compress hint); hard limit 5 MiB. About 30 new files per Space per hour, and 100 across the process (429). Nothing is stored on the API disk. Needs write scope. Not idempotent.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"filename": "<filename>",
"content_base64": "<content_base64>"
},
"name": "send_file"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| filename | Yes | File name to show recipients. | |
| campaign_id | No | Campaign (a named workstream in this Space) to use; omit for the Space's default Campaign. Ids come from list_campaigns. | |
| content_base64 | Yes | The file bytes, base64. Files are capped in size; large content belongs elsewhere with a link. | |
| idempotency_key | No | Optional. A string you generate once per intended action (a UUID is good) and repeat on retry. A retry with the same key and arguments returns the first result instead of acting twice; the same key with different arguments is refused. Kept 24 hours. |