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

# Download LQA Assessment XLSX reports

> Use this endpoint to export completed Language Quality Assessment (LQA) results as XLSX files for offline review, auditing, or integration with external quality management tools. Each XLSX report corresponds to one job part that has passed through an LQA workflow step in Phrase TMS.

When a single matching job part is found, the response is a single XLSX file. When multiple matching job parts are found, the response is a ZIP archive containing one XLSX file per job part. The response Content-Type is always application/octet-stream; the actual file format is conveyed by the filename extension in the Content-Disposition header.

If a given job part has not yet reached an LQA workflow step, reports from the next successive workflow step that has results may be returned instead. Job parts must share a workflow step and, unless multi-project LQA is enabled for your organization, a project; otherwise the endpoint returns 400. If no downloadable reports are found for any of the provided job part UIDs, the endpoint returns 404. Linguist users can only download reports when the project security settings permit it and LQA is enabled for the organization.

The returned filename is deterministic and cannot be customized through any request parameter. For a single job part it is LQA_{projectName}_{sourceLang}_{targetLang}_{jobFileName}.xlsx, with the full pre-extension string truncated to 250 characters. For multiple job parts it is LQA_{projectName}_{id}.zip, where {id} is an internal LQA-service batch identifier, not a project-level one. The only way to influence the filename is to rename the project or the job file before generating the report.



## OpenAPI

````yaml /openapi/phrase-tms-latest.json get /api2/v1/lqa/assessments/reports
openapi: 3.0.0
info:
  description: |-
    Welcome to Phrase's TMS API documentation. 

     Please visit our [help center](https://support.phrase.com/hc/en-us/sections/5709662083612) for more information about the APIs. 

     If you have any questions, please contact [Support](https://support.phrase.com/hc/requests/new). 

     Please, include the `User-Agent` header with the name of your application or project. It might be a good idea to include some sort of contact information as well, so that we can get in touch if necessary. Examples of excellent `User-Agent` headers:
     > User-Agent: Example mobile app (example@phrase.com) <br/> User-Agent: ACME Inc Java 1.8 Client (http://acmeinc.com/contact)
  version: Latest
  title: Phrase TMS API
servers:
  - url: https://cloud.memsource.com/web
security:
  - ApiToken: []
  - OAuth2: []
tags:
  - name: Additional Workflow Step
  - name: Analysis
  - name: Async Request
  - name: Authentication
  - name: Automations
  - name: Bilingual File
  - name: Business Unit
  - name: Buyer
  - name: Client
  - name: Connections
  - name: Connector
  - name: Conversations
  - name: Cost Center
  - name: Custom Fields
  - name: Custom File Type
  - name: Domain
  - name: Due Date Scheme
  - name: Email Template
  - name: File
  - name: Glossary
  - name: Import settings
  - name: Job
  - name: Language AI
  - name: Language Assets
  - name: Language Quality Assessment
  - name: Machine Translation
  - name: Machine Translation Settings
  - name: Mapping
  - name: Metabase
  - name: Net Rate Scheme
  - name: Notifications
  - name: Price List
  - name: Project
  - name: Project Template
  - name: Provider
  - name: Quality Assurance
  - name: Quality Profile
  - name: Quote
  - name: Reference File
  - name: Segment
  - name: Segmentation Rules
  - name: Service
  - name: Setup
  - name: Spell Check
  - name: SubDomain
  - name: Supported Languages
  - name: Term Base
  - name: Translation
  - name: Translation Memory
  - name: User
  - name: User Profile
  - name: Vendor
  - name: Webhook
  - name: Workflow Step
  - name: Workflow changes
  - name: XML Assistant
paths:
  /api2/v1/lqa/assessments/reports:
    get:
      tags:
        - Language Quality Assessment
      summary: Download LQA Assessment XLSX reports
      description: >-
        Use this endpoint to export completed Language Quality Assessment (LQA)
        results as XLSX files for offline review, auditing, or integration with
        external quality management tools. Each XLSX report corresponds to one
        job part that has passed through an LQA workflow step in Phrase TMS.


        When a single matching job part is found, the response is a single XLSX
        file. When multiple matching job parts are found, the response is a ZIP
        archive containing one XLSX file per job part. The response Content-Type
        is always application/octet-stream; the actual file format is conveyed
        by the filename extension in the Content-Disposition header.


        If a given job part has not yet reached an LQA workflow step, reports
        from the next successive workflow step that has results may be returned
        instead. Job parts must share a workflow step and, unless multi-project
        LQA is enabled for your organization, a project; otherwise the endpoint
        returns 400. If no downloadable reports are found for any of the
        provided job part UIDs, the endpoint returns 404. Linguist users can
        only download reports when the project security settings permit it and
        LQA is enabled for the organization.


        The returned filename is deterministic and cannot be customized through
        any request parameter. For a single job part it is
        LQA_{projectName}_{sourceLang}_{targetLang}_{jobFileName}.xlsx, with the
        full pre-extension string truncated to 250 characters. For multiple job
        parts it is LQA_{projectName}_{id}.zip, where {id} is an internal
        LQA-service batch identifier, not a project-level one. The only way to
        influence the filename is to rename the project or the job file before
        generating the report.
      operationId: downloadLqaReports
      parameters:
        - name: jobParts
          in: query
          description: Comma-separated list of job part UIDs.
          required: true
          example: KV7zn4sdgOBiMkp6Mf3rU2,LM9xa1bcPCjNlqr8Ng4sV3
          schema:
            type: string
            minLength: 1
            maxLength: 2147483647
      responses:
        '200':
          description: OK
        '400':
          description: >-
            Bad Request — jobParts missing or empty, or job parts mix workflow
            steps (or projects)
        '401':
          description: Not authorized
        '403':
          description: >-
            Forbidden — linguist users require the project to allow LQA report
            downloads and LQA must be enabled for the organization
        '404':
          description: >-
            Not Found — no downloadable LQA reports exist for any of the
            provided job part UIDs
        '405':
          description: Method not allowed
        '408':
          description: Timeout
        '410':
          description: Gone
        '415':
          description: Unsupported media type
        '429':
          description: Too many requests
        '500':
          description: Internal server error
        '501':
          description: Not implemented
components:
  securitySchemes:
    ApiToken:
      description: >-
        Get a token from `auth/login` [endpoint](#operation/login) and then pass
        it in the `Authorization` HTTP header in every subsequent API call. For
        more information visit our [help
        center](https://support.phrase.com/hc/en-us/articles/5709662181404-API-Authentication-TMS-#token-0-0).
      type: apiKey
      name: Authorization
      in: header
    OAuth2:
      description: >-
        A standard OAuth 2.0 authorization code flow. For more information visit
        our [help
        center](https://support.phrase.com/hc/en-us/articles/5709662181404-API-Authentication-TMS-#oauth-2-0-0-1).
      type: oauth2
      flows:
        authorizationCode:
          authorizationUrl: https://cloud.memsource.com/web/oauth/authorize
          tokenUrl: https://cloud.memsource.com/web/oauth/token
          scopes: {}

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.