Visier Table Source API

Use row-based management for your source data in Visier. The Table Source API supports direct SQL-based data modifications, eliminating concerns about file management or override behavior. Use the API to create, modify, and delete tables. Use SQL statements to query, insert, update, delete, and merge data into tables with transactions. You can reference the tables by mappings, just like other sources, to load data into an analytic object in a data version. **Note:** This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.

Operations 16

GET /v1alpha/data/table-sources/tables Retrieve table sources #
POST /v1alpha/data/table-sources/tables Create a table source #
GET /v1alpha/data/table-sources/tables/{tableId} Retrieve a table source #
PUT /v1alpha/data/table-sources/tables/{tableId} Update a table source #
DELETE /v1alpha/data/table-sources/tables/{tableId} Delete a table source #
GET /v1alpha/data/table-sources/tables/{tableId}/metadata Retrieve a table source's metadata #
POST /v1alpha/data/table-sources/tables/{tableId}/regenerate Regenerate a materialized view #
POST /v1alpha/data/table-sources/transactions Start a transaction #
GET /v1alpha/data/table-sources/transactions/{transactionId} Retrieve a transaction's status #
POST /v1alpha/data/table-sources/transactions/{transactionId}/extend Extend a transaction's expiry #
PUT /v1alpha/data/table-sources/transactions/{transactionId}/inputs/{filename} Upload an input file to a transaction #
POST /v1alpha/data/table-sources/transactions/{transactionId}/jobs Run a SQL job within a transaction #
GET /v1alpha/data/table-sources/transactions/{transactionId}/jobs/{jobId} Retrieve a job's status #
GET /v1alpha/data/table-sources/transactions/{transactionId}/outputs/{filename} Download an output file from a transaction #
GET /v1alpha/data/table-sources/transactions/{transactionId}/outputs/{filename}/parts List output file parts #
GET /v1alpha/data/table-sources/transactions/{transactionId}/outputs/{filename}/parts/{partIndex} Download an output file part #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/visier-tablesource-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

visier-tablesource-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Visier Data In Table Source API
  description: Visier APIs for sending data to Visier and running data load jobs.
  license:
    name: Apache License, Version 2.0
    url: https://www.apache.org/licenses/LICENSE-2.0
  version: 22222222.99201.3040
security:
- ApiKeyAuth: []
  BearerAuth: []
- ApiKeyAuth: []
  CookieAuth: []
- ApiKeyAuth: []
  OAuth2Auth: []
tags:
- name: TableSource
  x-displayName: Table Source
  description: 'Use row-based management for your source data in Visier. The Table Source API supports direct SQL-based data modifications, eliminating concerns about file management or override behavior. Use the API to create, modify, and delete tables. Use SQL statements to query, insert, update, delete, and merge data into tables with transactions. You can reference the tables by mappings, just like other sources, to load data into an analytic object in a data version.

    <br><br>

    **Note:** <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.</em>'
paths:
  /v1alpha/data/table-sources/tables:
    get:
      tags:
      - TableSource
      summary: Retrieve table sources
      description: "Retrieve a list of table source configurations. Table sources are SQL-accessible tables that can store and manage data directly within Visier.\n \n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_GetTableSources
      parameters:
      - name: limit
        in: query
        description: The maximum number of table sources to return. Default is 100.
        schema:
          type: integer
          format: int32
      - name: start
        in: query
        description: The index to start retrieving results from, also known as offset. The index begins at 0.
        schema:
          type: integer
          format: int32
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/servicing.sqlsource.SqlSourceTableListResponseDTO'
    post:
      tags:
      - TableSource
      summary: Create a table source
      description: "Create a table source configuration. Table sources define the structure and metadata for SQL-accessible tables in Visier.\n\n When creating objects, assign a unique object name but don't set a UUID. Visier generates UUIDs for new objects.\n \n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_CreateTableSource
      parameters:
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/servicing.sqlsource.SqlSourceTableDTO'
        required: true
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/servicing.sqlsource.SqlSourceTableDTO'
  /v1alpha/data/table-sources/tables/{tableId}:
    get:
      tags:
      - TableSource
      summary: Retrieve a table source
      description: "Retrieve a specific table source configuration by its unique identifier.\n \n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_GetTableSource
      parameters:
      - name: tableId
        in: path
        description: The unique identifier of the table source.
        required: true
        schema:
          type: string
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/servicing.sqlsource.SqlSourceTableDTO'
    put:
      tags:
      - TableSource
      summary: Update a table source
      description: "Update an existing table source configuration. Use this to modify the structure, columns, or metadata of a table source.\n \n In `PUT` requests, the definition in your API call replaces the prior definition. You must provide the entire definition in the `PUT` call. If you omit values from the update request, those values are removed from the table source. \n \n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_UpdateTableSource
      parameters:
      - name: tableId
        in: path
        description: The unique identifier of the table source to update.
        required: true
        schema:
          type: string
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/servicing.sqlsource.SqlSourceTableDTO'
        required: true
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/servicing.sqlsource.SqlSourceTableDTO'
    delete:
      tags:
      - TableSource
      summary: Delete a table source
      description: "Delete a table source configuration. This removes the table source definition but does not delete the associated data.\n \n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_DeleteTableSource
      parameters:
      - name: tableId
        in: path
        description: The unique identifier of the table source.
        required: true
        schema:
          type: string
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content: {}
  /v1alpha/data/table-sources/tables/{tableId}/metadata:
    get:
      tags:
      - TableSource
      summary: Retrieve a table source's metadata
      description: "Retrieve previously-stored metadata for a table source, such as the key-value pairs to apply to the table if you commit the transaction. To store metadata for a table source, use the `setMetadata` action in `POST /v1alpha/data/table-sources/transactions/{transactionId}/jobs`.\n\n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_GetTableSourceMetadata
      parameters:
      - name: tableId
        in: path
        description: The unique identifier of the table source for which to retrieve metadata.
        required: true
        schema:
          type: string
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/servicing.sqlsource.SqlSourceGetTableMetadataResponseDTO'
  /v1alpha/data/table-sources/tables/{tableId}/regenerate:
    post:
      tags:
      - TableSource
      summary: Regenerate a materialized view
      description: "Run a SQL job to manually refresh the dataset during troubleshooting, query updates, or when manual data fetching is required.\n\n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_RegenerateMaterializedView
      parameters:
      - name: tableId
        in: path
        description: The unique identifier of the table source.
        required: true
        schema:
          type: string
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/data_in.TableSourceRequest'
        required: true
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/servicing.sqlsource.SqlSourceExecuteJobResponseDTO'
  /v1alpha/data/table-sources/transactions:
    post:
      tags:
      - TableSource
      summary: Start a transaction
      description: "Start a transaction for SQL operations on table sources. Transactions provide isolation for multiple operations and allow for rollback if needed.\n\n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_BeginTransaction
      parameters:
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/servicing.sqlsource.SqlSourceBeginTransactionRequestDTO'
        required: true
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/servicing.sqlsource.SqlSourceTransactionStateDTO'
  /v1alpha/data/table-sources/transactions/{transactionId}:
    get:
      tags:
      - TableSource
      summary: Retrieve a transaction's status
      description: "Retrieve the current status and details of a specific transaction. If the transaction was dispatched to analytic tenants, the response includes the status of each analytic tenant's transaction in the `children` field.\n\n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_GetTransaction
      parameters:
      - name: transactionId
        in: path
        description: The unique identifier of the transaction.
        required: true
        schema:
          type: string
      - name: summaryOnly
        in: query
        description: If `true`, the response omits the `children` array and returns only the `summary` counts. Use for polling. Default is `false`.
        schema:
          type: boolean
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/servicing.sqlsource.SqlSourceTransactionStateDTO'
  /v1alpha/data/table-sources/transactions/{transactionId}/extend:
    post:
      tags:
      - TableSource
      summary: Extend a transaction's expiry
      description: "Extend the expiry time of an open transaction.\n\n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_ExtendTransaction
      parameters:
      - name: transactionId
        in: path
        description: The unique identifier of the transaction to extend.
        required: true
        schema:
          type: string
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/servicing.sqlsource.SqlSourceExtendTransactionRequestDTO'
        required: true
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/servicing.sqlsource.SqlSourceTransactionStateDTO'
  /v1alpha/data/table-sources/transactions/{transactionId}/inputs/{filename}:
    put:
      tags:
      - TableSource
      summary: Upload an input file to a transaction
      description: "Send input files to a transaction. SQL operations can reference an input file within a job as if it were a local, temporary view. For example, the input file can contain data to insert into your sources, IDs to match against to change or delete rows, or any other input for your SQL query.\n \n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_UploadInputFile
      parameters:
      - name: transactionId
        in: path
        description: The unique identifier of the transaction.
        required: true
        schema:
          type: string
      - name: filename
        in: path
        description: The name of the file to upload. The input will be accessible with this filename during job execution.
        required: true
        schema:
          type: string
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content: {}
      requestBody:
        content:
          multipart/form-data:
            schema:
              type: object
              properties:
                file:
                  type: string
                  format: binary
                  description: The input file to upload. The file is accessible during SQL job execution as a temporary view using the provided filename.
  /v1alpha/data/table-sources/transactions/{transactionId}/jobs:
    post:
      tags:
      - TableSource
      summary: Run a SQL job within a transaction
      description: "Execute a SQL job within a transaction. Jobs can contain multiple SQL operations including queries, inserts, updates, deletes, and merge operations.\n \n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_ExecuteJob
      parameters:
      - name: transactionId
        in: path
        description: The unique identifier of the transaction.
        required: true
        schema:
          type: string
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/servicing.sqlsource.SqlSourceExecuteJobRequestDTO'
        required: true
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/servicing.sqlsource.SqlSourceExecuteJobResponseDTO'
  /v1alpha/data/table-sources/transactions/{transactionId}/jobs/{jobId}:
    get:
      tags:
      - TableSource
      summary: Retrieve a job's status
      description: "Retrieve the status of a SQL job and any child jobs spawned from it. Use the job ID returned by `POST /v1alpha/data/table-sources/transactions/{transactionId}/jobs` to retrieve the job's status.\n\n If the job was dispatched across multiple tenants, the response includes per-tenant status details along with aggregated summary counts.\n\n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_GetJobStatus
      parameters:
      - name: transactionId
        in: path
        description: The unique identifier of the transaction.
        required: true
        schema:
          type: string
      - name: jobId
        in: path
        description: The unique identifier of the job.
        required: true
        schema:
          type: string
      - name: summaryOnly
        in: query
        description: "If `true`, the response includes the overall status and summary counts,\n and omits per-tenant job statuses. Useful for large multi-tenant jobs. Default is `false`."
        schema:
          type: boolean
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/servicing.sqlsource.SqlSourceGetJobStatusResponseDTO'
  /v1alpha/data/table-sources/transactions/{transactionId}/outputs/{filename}:
    get:
      tags:
      - TableSource
      summary: Download an output file from a transaction
      description: "Download an output file generated by a SQL operation within a transaction. To generate output files, use the `QUERY` action and `output` parameter in `POST /v1alpha/data/table-sources/transactions/{transactionId}/jobs`.\n\n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_DownloadOutputFile
      parameters:
      - name: transactionId
        in: path
        description: The unique identifier of the transaction.
        required: true
        schema:
          type: string
      - name: filename
        in: path
        description: The name of the file to download. This should be the filename specified in an output of an action during job execution.
        required: true
        schema:
          type: string
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: File contents
          content:
            '*/*':
              schema:
                type: string
                format: binary
  /v1alpha/data/table-sources/transactions/{transactionId}/outputs/{filename}/parts:
    get:
      tags:
      - TableSource
      summary: List output file parts
      description: "List the parts of a multi-part output file. SQL operations generate output files within a transaction. Each part is a complete, self-contained file in the output format. Parts are 0-indexed. For an output with `numberOfParts: 3`, the part numbers are 0, 1, and 2.  For large output files, download by file part for better performance.\n\n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_ListOutputFileParts
      parameters:
      - name: transactionId
        in: path
        description: The unique identifier of the transaction.
        required: true
        schema:
          type: string
      - name: filename
        in: path
        description: The name of the output file to list parts for.
        required: true
        schema:
          type: string
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/servicing.sqlsource.SqlSourceListOutputFilePartsResponseDTO'
  /v1alpha/data/table-sources/transactions/{transactionId}/outputs/{filename}/parts/{partIndex}:
    get:
      tags:
      - TableSource
      summary: Download an output file part
      description: "Download a single part of a multi-part output file. SQL operations generate output files within a transaction. Each part is a complete, self-contained file in the output format. Parts are 0-indexed. For an output with `numberOfParts: 3`, the part numbers are 0, 1, and 2.  For large output files, download by file part for better performance.\n\n <br>**Note**: <em>This API is in **alpha**. While in alpha, APIs may change in a breaking way without notice; functionality may be removed, and no deprecation notices will be issued.\n If you are interested in using this API, please contact your Customer Success Manager (CSM).</em>"
      operationId: TableSource_DownloadOutputFilePart
      parameters:
      - name: transactionId
        in: path
        description: The unique identifier of the transaction.
        required: true
        schema:
          type: string
      - name: filename
        in: path
        description: The name of the output file to download a part of.
        required: true
        schema:
          type: string
      - name: partIndex
        in: path
        description: The zero-based index of the part to download.
        required: true
        schema:
          type: integer
          format: int32
      - name: TargetTenantID
        in: header
        description: Optionally, specify the tenant that you want to execute the API call on. This defines the tenant that you're logged into. If omitted, the request uses the administrating tenant as the login tenant.
        schema:
          type: string
      responses:
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
        '200':
          description: File contents
          content:
            '*/*':
              schema:
                type: string
                format: binary
components:
  schemas:
    servicing.sqlsource.SqlSourceColumnDTO:
      type: object
      properties:
        name:
          type: string
          description: The name of the column. This is used in SQL queries to refer to the column.
        dataType:
          enum:
          - UNSPECIFIED
          - STRING
          - TENANT_ID
          - CUSTOMER_ID
          - INTEGER
          - LONG
          - DOUBLE
          - DECIMAL
          - BOOLEAN
          - DATE_TIME
          - DATE
          - JSON
          - BINARY
          type: string
          description: "The SQL type of data stored in the column.\n * `UNSPECIFIED`: The data type is unspecified.\n * `STRING`: The data type is a string.\n * `TENANT_ID`: The data type is a tenant code with the administrating tenant code prefix. Example: If the full tenant code is `WFF_j1r~c7o`, the tenant ID is `WFF_j1r~c7o`. If `CUSTOMER_ID` is specified, do not specify `TENANT_ID`.\n * `CUSTOMER_ID`: The data type is an analytic tenant code without the administrating tenant code prefix. Use customer ID to filter inherited data by tenant. Example: If the full tenant code is `WFF_j1r~c7o`, the customer ID is `c7o`. If `TENANT_ID` is specified, do not specify `CUSTOMER_ID`.\n * `INTEGER`: The data type is an integer.\n * `LONG`: The data type is a long value.\n * `DOUBLE`: The data type is a double.\n * `DECIMAL`: The data type is a decimal.\n * `BOOLEAN`: The data type is a Boolean value.\n * `DATE_TIME`: The data type is a date and time value. \n * `DATE`: The data type is date.\n * `JSON`: The data type is in JSON format.\n * `BINARY`: The data type is a binary blob."
          format: enum
        isPrimaryTimestamp:
          type: boolean
          description: If `true`, this column determines the overall timestamp of the data contained within the row. This is used for time-based partitioning.
    servicing.sqlsource.SqlSourceListOutputFilePartsResponseDTO:
      type: object
      properties:
        transactionId:
          type: string
          description: The transaction ID the output file belongs to.
        filename:
          type: string
          description: The name of the output file.
        numberOfParts:
          type: integer
          description: The number of parts that are available for the output file. The parts are numbered from 0 up to (but not including) this number.
          format: int32
    servicing.sqlsource.SqlSourceGetJobStatusResponseDTO:
      type: object
      properties:
        status:
          enum:
          - UNKNOWN
          - PENDING
          - RUNNING
          - SUCCEEDED
          - FAILED
          type: string
          description: The overall status of the jobs, including children of the requested job.
          format: enum
        summary:
          allOf:
          - $ref: '#/components/schemas/servicing.sqlsource.SqlSourceJobStatusSummaryDTO'
          description: Summary of job statuses for SQL jobs.
        processingSummary:
          allOf:
          - $ref: '#/components/schemas/servicing.sqlsou

# --- truncated at 32 KB (58 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/visier/refs/heads/main/openapi/visier-tablesource-api-openapi.yml