> ## Documentation Index > Fetch the complete documentation index at: https://docs.neuracall.com/llms.txt > Use this file to discover all available pages before exploring further. # Listar Análisis > Returns a paginated list of call analysis requests for your account. Filter results by date range and analysis model. Results include status, scores, and metadata for each analyzed call. ## OpenAPI ````yaml GET /v1/call-analysis openapi: 3.0.2 info: title: Neuracall API description: >- ## Overview The Neuracall API provides powerful call analysis capabilities for contact centers and customer service teams. Submit audio recordings and receive detailed analysis including: - **Transcription**: Accurate speech-to-text conversion - **Quality Scoring**: Automated evaluation against customizable criteria - **Insights & Keywords**: AI-extracted conversation highlights - **Statistics**: Aggregated performance metrics ## Authentication All API endpoints (except `/v1/auth`) require a Bearer token. Obtain your token using the Authentication endpoint with your client credentials. ``` Authorization: Bearer ``` ## Support For questions or issues, contact support@neuracall.com contact: name: Neuracall Support url: https://neuracall.com/support email: support@neuracall.com license: name: Proprietary url: https://neuracall.com/license version: 1.0.0 servers: [] security: [] tags: - name: Authentication description: >- Obtain access tokens to authenticate your application. Required before making other API calls. - name: Analysis Models description: >- Manage analysis models that define evaluation criteria and scoring parameters for call analysis. - name: Model Categories description: >- Manage categories within analysis models. Categories group related evaluation variables and help organize the scoring structure. - name: Model Variables description: >- Manage evaluation variables within analysis models. Variables define specific scoring criteria used during call analysis. - name: Model Metadata description: >- Manage metadata fields within analysis models. Metadata defines additional information required when submitting calls for analysis (e.g., campaign, department). - name: Call Analysis description: >- Submit audio recordings for analysis and retrieve results including transcriptions, scores, and insights. - name: Statistics description: >- Retrieve aggregated statistics and performance metrics from analyzed calls for dashboards and reporting. paths: /v1/call-analysis: get: tags: - Call Analysis summary: Retrieve all call analysis requests description: >- Returns a paginated list of call analysis requests for your account. Filter results by date range and analysis model. Results include status, scores, and metadata for each analyzed call. operationId: List_Call_Analyses_v1_call_analysis_get parameters: - description: Filter by analysis model ID required: false schema: title: Model Id type: integer description: Filter by analysis model ID example: 1 name: model_id in: query - description: Filter calls created on or after this date (UTC) required: false schema: title: Start Date type: string description: Filter calls created on or after this date (UTC) format: date-time example: '2024-01-01T00:00:00Z' name: start_date in: query - description: Filter calls created on or before this date (UTC) required: false schema: title: End Date type: string description: Filter calls created on or before this date (UTC) format: date-time example: '2024-12-31T23:59:59Z' name: end_date in: query - description: Page number (0-indexed) required: false schema: title: Page minimum: 0 type: integer description: Page number (0-indexed) default: 0 example: 0 name: page in: query - description: Number of items per page required: false schema: title: Size maximum: 100 minimum: 1 type: integer description: Number of items per page default: 20 example: 20 name: size in: query responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/PaginationResult' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - HTTPBearer: [] components: schemas: PaginationResult: title: PaginationResult required: - content type: object properties: content: title: Content type: array items: {} description: List of items for the current page page: title: Page type: integer description: Current page number (0-indexed) example: 0 size: title: Size type: integer description: Number of items requested per page example: 20 content_length: title: Content Length type: integer description: Actual number of items in the current page example: 20 total_elements: title: Total Elements type: integer description: Total number of items across all pages example: 1250 total_pages: title: Total Pages type: integer description: Total number of pages available example: 63 description: Paginated response wrapper for list endpoints ErrorResponse: title: ErrorResponse required: - code - message type: object properties: code: title: Code type: string description: Error code for programmatic handling example: 001-001-0001 path: title: Path type: string description: Field path for validation errors example: body.external_id message: title: Message type: string description: Human-readable error message example: The requested resource was not found description: Standard error response format for API errors example: code: 001-001-0001 message: The requested resource was not found HTTPValidationError: title: HTTPValidationError type: object properties: detail: title: Detail type: array items: $ref: '#/components/schemas/ValidationError' ValidationError: title: ValidationError required: - loc - msg - type type: object properties: loc: title: Location type: array items: anyOf: - type: string - type: integer msg: title: Message type: string type: title: Error Type type: string securitySchemes: HTTPBearer: type: http scheme: bearer ````