Skip to main content
GET
/
v1
/
connectors
/
{connector_id}
/
{connection_id}
/
operations
List Operations
curl --request GET \
  --url https://api.example.com/v1/connectors/{connector_id}/{connection_id}/operations \
  --header 'x-api-key: <api-key>'
[
  {
    "id": "<string>",
    "operationId": "<string>",
    "path": "<string>",
    "method": "<string>",
    "summary": "<string>",
    "description": "<string>",
    "tags": [],
    "pretty_name": "<string>",
    "pretty_description": "<string>"
  }
]
List all available API operations (endpoints) for a specific connector connection. Operations define the actions you can perform through the connector — for example, sending a Slack message or creating a Jira ticket.

​
Path Parameters

​
connector_id
string
required
Unique identifier of the connector
​
connection_id
string
required
Unique identifier of the connection

​
Response

Returns an array of ConnectorOperationItem objects.
​
id
string
Internal catalog ID of the operation
​
operationId
string
OpenAPI operation identifier
​
path
string
API path for the operation
​
method
string
HTTP method (GET, POST, PUT, DELETE, PATCH)
​
summary
string
Brief summary of the operation
​
description
string
Detailed description of what the operation does
​
tags
array
Tags categorizing the operation
​
pretty_name
string
Human-friendly display name for the operation

​
Example Request

curl -X GET -H "x-api-key: <your-api-key>" \
  "https://api.xpander.ai/v1/connectors/<connector-id>/<connection-id>/operations"

​
Notes

  • Use operation IDs when configuring agent attached_tools
  • The id field is the catalog identifier used internally; operationId is the OpenAPI identifier

Authorizations

​
x-api-key
string
header
required

API Key for authentication

Path Parameters

​
connector_id
string
required
​
connection_id
string
required

Response

Successful Response

​
id
string
required

Unique identifier for this operation. Use this as item_id when adding the operation to an agent's tool graph.

​
operationId
string
required

The OpenAPI operationId — a stable, human-readable identifier for this endpoint (e.g., 'sendMessage', 'createIssue').

​
path
string
required

API endpoint path (e.g., '/api/v1/messages', '/rest/api/3/issue'). May contain path parameters in {brackets}.

​
method
string
required

HTTP method for this operation (GET, POST, PUT, DELETE, PATCH).

​
summary
string | null

Brief one-line summary of what this operation does.

​
description
string | null

Detailed description of the operation, including parameters, behavior, and response format.

​
tags
string[] | null

Categorization tags for grouping related operations (e.g., 'Messages', 'Users', 'Issues').

​
pretty_name
string | null

Human-friendly name for the operation (e.g., 'Send Message', 'Create Issue'). More readable than the operationId.

​
pretty_description
string | null

Enhanced description of the operation, potentially AI-generated for better clarity.