> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xpander.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Connector Operation Schema

> Get an operation's input/output schema. input is a JSON schema grouping query_params/path_params/body_params - the same structure Invoke Connector Operation accepts; output is the operation's success (2xx application/json) response schema. All $ref references are resolved inline.

`operation_id` accepts the operation's `id` or `operationId` from [List Connector Operations](/api-reference/v1/tools/list-connector-operations). Pass `_` as `connector_id` to resolve it from the connection.


## OpenAPI

````yaml GET /v1/tools/connectors/{connector_id}/connections/{connection_id}/{operation_id}/schema
openapi: 3.1.0
info:
  title: xpander.ai API Service
  description: |2-

        The xpander.ai API Service provides a unified REST API for managing AI agents,
        executing tasks, managing knowledge bases, and integrating with external systems.
        
        Features:
        - Agent Management: Create, update, deploy, and delete AI agents
        - Task Execution: Invoke agents with support for sync, async, and streaming modes
        - Knowledge Bases: Manage knowledge bases and documents for RAG workflows
        - Tools: Discover, connect, and attach tools (connectors, custom functions, MCP servers, sub-agents, workflows) to agents and workflows
        - MCP Integration: Model Context Protocol support for standardized AI interactions
        
        Authentication: All endpoints require authentication via either an API key (`x-api-key`) or an OAuth2 JWT (`Authorization: Bearer <jwt>`).
        
  version: '0.001'
servers: []
security: []
paths:
  /v1/tools/connectors/{connector_id}/connections/{connection_id}/{operation_id}/schema:
    get:
      tags:
        - API v1
        - Tools
        - Tools Discovery
      summary: Get Connector Operation Schema
      description: >-
        Get an operation's input/output schema. `input` is a JSON schema
        grouping the operation's inputs into
        `query_params`/`path_params`/`body_params` (the same structure the
        invoke endpoint accepts); `output` is the operation's success (2xx
        application/json) response schema. All $ref references are resolved
        inline. `operation_id` accepts the operation's `id` or `operationId`;
        pass `_` as connector_id to resolve it from the connection.
      operationId: >-
        Get_connector_operation_schema_v1_tools_connectors__connector_id__connections__connection_id___operation_id__schema_get
      parameters:
        - name: connector_id
          in: path
          required: true
          schema:
            type: string
            title: Connector Id
        - name: connection_id
          in: path
          required: true
          schema:
            type: string
            title: Connection Id
        - name: operation_id
          in: path
          required: true
          schema:
            type: string
            title: Operation Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - APIKeyHeader: []
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      description: API Key for authentication
      in: header
      name: x-api-key

````