> ## Documentation Index > Fetch the complete documentation index at: https://docs.julian.11x.ai/llms.txt > Use this file to discover all available pages before exploring further. # List agent extracted variables > Returns the non-deleted, customer-defined variables that Julian extracts from the agent's conversations. System-default definitions are excluded. Dropdown and date/time variables include their type-specific configuration. ## OpenAPI ````yaml /openapi.json get /agents/{agentId}/extracted-variables openapi: 3.1.0 info: title: Julian API version: 1.0.0 description: >- API for Julian, 11x's AI calling platform. Programmatically enroll contacts into agent calling sequences, manage sequences, and track credit usage. All requests are authenticated with an organization API key in the `x-api-key` header and rate limited to 10 requests per second per key (HTTP 429 when exceeded). servers: - url: https://julian.11x.ai/api/v1 security: - apiKeyAuth: [] tags: - name: Scheduling description: Enroll contacts into an agent's calling sequence. - name: Sequences description: Manage active sequences. - name: Agents description: Read agent configuration. - name: Conversation Meetings description: >- Manage the meeting booked during a conversation — list its attendees, add attendees before it starts, and cancel it. Every endpoint is addressed by an `entityId` that identifies the conversation. Today only voice calls are supported, with the form of the call prefix followed by the call ID (e.g. `call.abc123`). The meeting is resolved from the calendar booking created during the conversation, and the calendar provider remains the source of truth. - name: Conversation Metadata description: >- Retrieve completed conversation data asynchronously — designed for batch ingestion, backfills, and reconciliation jobs that pull conversation metadata instead of receiving it through a webhook. **Recommended batch ingestion flow:** 1. Call `GET /conversations/search/{agentId}` with the time window you want to ingest (e.g. yesterday or the last seven days). 2. Iterate through the returned `sequenceIds`. 3. For each sequence ID, call `GET /conversations/metadata/{sequenceId}`. 4. Store the returned `metadata` array in your warehouse. 5. Use `limit`, `offset`, and `hasMore` to paginate through larger backfills. - name: Credits description: Track credit utilization. - name: Webhooks description: Events Julian sends to your endpoint. paths: /agents/{agentId}/extracted-variables: get: tags: - Agents summary: List agent extracted variables description: >- Returns the non-deleted, customer-defined variables that Julian extracts from the agent's conversations. System-default definitions are excluded. Dropdown and date/time variables include their type-specific configuration. operationId: listAgentExtractedVariables parameters: - $ref: '#/components/parameters/AgentId' responses: '200': description: >- Customer-defined extracted-variable definitions configured on the agent. content: application/json: schema: type: object required: - extractedVariables properties: extractedVariables: type: array items: $ref: '#/components/schemas/ExtractedVariableDefinition' '401': description: >- `UNAUTHORIZED` or `INVALID_API_KEY` — the API key is missing or invalid, or the agent does not exist or belong to the API key's organization. content: application/json: schema: $ref: '#/components/schemas/Error' '500': $ref: '#/components/responses/InternalServerError' components: parameters: AgentId: name: agentId in: path required: true description: ID of the agent, e.g. `agent.abc123`. schema: type: string schemas: ExtractedVariableDefinition: type: object required: - slug - displayName - description - type properties: slug: type: string description: Stable key used for this value in conversation results. example: meeting_time displayName: type: string description: Human-readable variable name. example: Meeting time description: type: string description: Explanation of the value Julian extracts. example: The agreed date and time for the meeting type: type: string description: Value type extracted from the conversation. enum: - TEXT - NUMBER - TRUE/FALSE - DATE/TIME - DROPDOWN example: DATE/TIME dropdownOptions: type: array description: Allowed values. Returned only when `type` is `DROPDOWN`. items: type: string example: - High - Medium - Low datetimeFormat: type: - string - 'null' description: >- Moment.js-compatible output format. Returned only when `type` is `DATE/TIME`. enum: - YYYY-MM-DD - MMMM Do, YYYY - D MMM YYYY - D MMMM YYYY - h:mm A - HH:mm - YYYY-MM-DD h:mm A - YYYY-MM-DD HH:mm:ss - YYYY-MM-DD h:mm:ss A - null example: YYYY-MM-DD HH:mm:ss formatDatetimeInUtc: type: - boolean - 'null' description: >- Whether the extracted value is normalized to UTC. Returned only when `type` is `DATE/TIME`. example: true Error: type: object required: - error - message properties: error: type: string description: Machine-readable error code. example: INVALID_PHONE_NUMBER message: type: string description: Human-readable explanation. responses: InternalServerError: description: >- `INTERNAL_SERVER_ERROR` — unexpected server error. Retry with backoff and contact the 11x team if it persists. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: INTERNAL_SERVER_ERROR message: Internal Server Error. Please contact 11x team. securitySchemes: apiKeyAuth: type: apiKey in: header name: x-api-key description: Organization API key. Get it from the 11x team or from the platform. ````