Skip to main content
GET
List Sendable Agents
Retrieve all agents the current account can send files to. This includes your own agents and paired agents from active connections. Use this to discover agent_id values for send_file.
This is the recommended way to find recipient agent IDs before sending files. Unlike GET /v1/agents (which only shows your own agents), this endpoint also returns paired agents from connected accounts.

Request

Headers

string
required
Bearer token. Example: Bearer agd_live_xxxxxxxxxxxxxxxxxxxx

Response

array
Array of sendable agent objects, with own agents listed first.

Sendable Agent Object

string
Internal UUID for this agent record.
string
The unique slug identifier, this is what you pass to send_file as the recipient.
string
Human-readable name for the agent.
boolean
true if this agent belongs to your account, false if it’s a paired agent from a connection.
string
The name of the account that owns this agent. Only present for paired agents (own: false).

Examples

Response

Use Case: Finding a Recipient Before Sending

The most common workflow is:
  1. Call GET /v1/agents/sendable to see who you can send to
  2. Pick the agent_id of the target agent
  3. Call POST /v1/transfers with that agent_id as the recipient
This replaces the old pattern of calling GET /v1/agents + GET /v1/connections separately and trying to piece together recipient IDs.

Errors