Skip to main content
POST
Create Transfer
Upload one or more files and create a transfer that a recipient agent can download.
Use the SDK, not this endpoint directly. The AgentDrop Python SDK and Node.js SDK wrap this endpoint and handle X25519 key exchange, AES-256-GCM encryption, pairwise channel derivation, and Shield scanning automatically. Calling this endpoint directly skips all of that, your files will be uploaded as plaintext and downloads will not be scanned for prompt injection or malware. The endpoint is documented here for transparency, not because raw HTTP is a supported integration path.
This endpoint accepts multipart/form-data, not JSON. Files are uploaded directly in the request body.

Request

Headers

string
required
Bearer token. Example: Bearer agd_live_xxxxxxxxxxxxxxxxxxxx
string
required
Must be multipart/form-data

Body Parameters

string
required
Identifier for the sending agent. Free-form string used for tracking and filtering.
string
required
Identifier for the intended recipient agent.
string
Disambiguator when the same agent_id exists on multiple paired accounts. Accepts the recipient’s account email, account UUID, or account display name. Required only when /v1/agents/resolve returns AMBIGUOUS_RECIPIENT for the recipient. See the Ambiguous Recipients section below.
string
required
Transfer mode. One of: agent-to-agent, agent-to-human, human-to-agent.
file
required
One or more files to upload. Include multiple files fields for multiple files.
boolean
default:"false"
Whether the uploaded files are already encrypted with AES-256-GCM (done client-side before upload). The SDK always sets this to true and encrypts before calling the endpoint. If you call the API directly with is_encrypted=false, your files are stored on our servers as plaintext, do not do this for any file that matters.
string
Optional message to attach to the transfer.
boolean
default:"true"
Whether to automatically delete the transfer after first download.
integer
default:"10"
Maximum number of times the transfer can be downloaded before it locks.
string
default:"24h"
How long the transfer stays active. Examples: 1h, 12h, 24h, 7d, 30d. Maximum depends on your plan.

Response

string
Unique transfer ID. Example: tr_abc123
string
Human-readable URL for the transfer.
string
Direct API URL for programmatic access.
string
Transfer status. One of: active, pending_recipient, expired, deleted.pending_recipient means the recipient doesn’t have an AgentDrop account or hasn’t set a receiving password yet. They’ll be notified by email. The transfer activates automatically when they sign up and set their receiving password.
string|null
Present when status is pending_recipient. Explains why the transfer is pending and what the recipient needs to do.
string
The sender identifier provided in the request.
string
The recipient identifier provided in the request.
array
Array of uploaded file objects, each containing name, size, and type.
integer
Maximum allowed downloads.
integer
Current download count (starts at 0).
integer
Total size of all uploaded files in bytes.
string
ISO 8601 creation timestamp.
string
ISO 8601 timestamp when the transfer expires.
boolean
Whether the files are end-to-end encrypted.
boolean
Whether the transfer will be automatically deleted after expiry.
string|null
The message attached to the transfer, or null if none was provided.

Examples

Response

Errors

Ambiguous Recipients

An agent_id is unique within an account but can collide across accounts you’re paired with. If two paired accounts both use, say, claude-code-agent, the server refuses to pick one and returns:
Retry with recipient_account in the multipart body:
Emails in candidates are masked; the full address is never disclosed to the sender. If the recipient’s agent_id only exists on one paired account, recipient_account is ignored.

Agent-to-Human Transfers

When sending files to a human email (mode: agent-to-human), the behavior depends on the recipient’s account status: When a pending_recipient transfer activates (recipient signs up + sets password), files are re-encrypted with their public key and the server key is deleted. The recipient gets a “files ready” notification.
Transfers to non-registered emails are rate-limited to 5 per account per day to prevent abuse.