ThoughtSpot 26.4.0.cl API

openapi: 3.0.0
info:
  title: ThoughtSpot Public REST 10.1.0.cl 26.4.0.cl API
  version: '2.0'
servers:
- url: '{base-url}'
  variables:
    base-url:
      default: https://localhost:443
security:
- bearerAuth: []
tags:
- name: 26.4.0.cl
paths:
  /api/rest/2.0/collections/create:
    post:
      operationId: createCollection
      description: "\n <span class=\"since-beta-tag\">Version: 26.4.0.cl or later</span>\n\nCreates a new collection in ThoughtSpot.\n\nCollections allow you to organize and group related metadata objects such as Liveboards, Answers, worksheets, and other data objects. You can also create nested collections (sub-collections) to build a hierarchical structure.\n\n#### Supported operations\n\nThe API endpoint lets you perform the following operations:\n\n* Create a new collection\n* Add metadata objects (Liveboards, Answers, Logical Tables) to the collection\n* Create nested collections by adding sub-collections\n\n\n\n\n#### Endpoint URL\n"
      tags:
      - 26.4.0.cl
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateCollectionRequest'
        required: true
      parameters: []
      responses:
        '200':
          description: Collection created successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Collection'
        '400':
          description: Invalid request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Unexpected error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
  /api/rest/2.0/collections/delete:
    post:
      operationId: deleteCollection
      description: "\n <span class=\"since-beta-tag\">Version: 26.4.0.cl or later</span>\n\nDeletes one or more collections from ThoughtSpot.\n\n#### Delete options\n\n* **delete_children**: When set to `true`, deletes the child objects (metadata items) within the collection that the user has access to. Objects that the user does not have permission to delete will be skipped.\n* **dry_run**: When set to `true`, performs a preview of the deletion operation without actually deleting anything. The response shows what would be deleted, allowing you to review before committing the deletion.\n\n#### Response\n\nThe response includes:\n* **metadata_deleted**: List of metadata objects that were successfully deleted\n* **metadata_skipped**: List of metadata objects that were skipped due to lack of permissions or other constraints\n\n\n\n\n#### Endpoint URL\n"
      tags:
      - 26.4.0.cl
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/DeleteCollectionRequest'
        required: true
      parameters: []
      responses:
        '200':
          description: Collections deleted successfully.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CollectionDeleteResponse'
        '400':
          description: Invalid request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Resource not found.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Unexpected error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
  /api/rest/2.0/collections/search:
    post:
      operationId: searchCollections
      description: "\n <span class=\"since-beta-tag\">Version: 26.4.0.cl or later</span>\n\nGets a list of collections available in ThoughtSpot.\n\nTo get details of a specific collection, specify the collection GUID or name. You can also filter the API response based on the collection name pattern, author, and other criteria.\n\n#### Search options\n\n* **name_pattern**: Use '%' as a wildcard character to match collection names\n* **collection_identifiers**: Search for specific collections by their GUIDs or names\n* **include_metadata**: When set to `true`, includes the metadata objects within each collection in the response\n\n**NOTE**: In addition to the GUID and name, `collection_identifiers` accepts a Custom object ID if one is configured for the collection. The response also includes the `obj_id` field for each collection that has one set.\n\n**NOTE**: If the API returns an empty list, consider increasing the value of the `record_size` parameter. To search across all available collections, set `record_size` to `-1`.\n\n\n\n\n#### Endpoint URL\n"
      tags:
      - 26.4.0.cl
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SearchCollectionsRequest'
        required: true
      parameters: []
      responses:
        '200':
          description: Successfully retrieved list of collections
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CollectionSearchResponse'
        '400':
          description: Invalid request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Unexpected error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
  /api/rest/2.0/collections/{collection_identifier}/update:
    post:
      operationId: updateCollection
      description: "\n <span class=\"since-beta-tag\">Version: 26.4.0.cl or later</span>\n\nUpdates an existing collection in ThoughtSpot.\n\n#### Supported operations\n\nThis API endpoint lets you perform the following operations:\n\n* Update collection name and description\n* Change visibility settings\n* Add metadata objects to the collection (operation: ADD)\n* Remove metadata objects from the collection (operation: REMOVE)\n* Replace all metadata objects in the collection (operation: REPLACE)\n\n#### Operation types\n\n* **ADD**: Adds the specified metadata objects to the existing collection without removing current items\n* **REMOVE**: Removes only the specified metadata objects from the collection\n* **REPLACE**: Replaces all existing metadata objects with the specified items (default behavior)\n\n\n\n\n#### Endpoint URL\n"
      tags:
      - 26.4.0.cl
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpdateCollectionRequest'
        required: true
      parameters:
      - in: path
        name: collection_identifier
        required: true
        schema:
          type: string
        description: 'Unique GUID of the collection. Note: Collection names cannot be used as

          identifiers since duplicate names are allowed.'
      responses:
        '204':
          description: Collection updated successfully. No content returned.
        '400':
          description: Invalid request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Resource not found.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Unexpected error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
  /api/rest/2.0/jobs/history/communication-channels/search:
    post:
      operationId: searchChannelHistory
      description: "\n <span class=\"since-beta-tag\">Version: 26.4.0.cl or later</span>\n\nSearches delivery history for communication channels such as webhooks. Returns channel-level delivery status for each job execution record. Use this to monitor channel health and delivery success rates across events.\n\nRequires `ADMINISTRATION` (**Can administer ThoughtSpot**) or `DEVELOPER` (**Has developer privilege**) privilege. If [Role-Based Access Control (RBAC)](https://developers.thoughtspot.com/docs/rbac) is enabled on your instance, users with `CAN_MANAGE_WEBHOOKS` (**Can manage webhooks**) privilege are also authorized to perform this action.\n\n**NOTE**: When `channel_type` is `WEBHOOK`, the following constraints apply:\n\n- `job_ids`, `channel_identifiers`, and `events` each accept at most one element.\n- When `job_ids` is provided, it is used as the sole lookup key and other filter fields are ignored.\n- When `job_ids` is not provided, `channel_identifiers` and `events` are both required, each containing exactly one element.\n- Records older than the configured retention period are not returned.\n- Use `start_epoch_time_in_millis` and/or `end_epoch_time_in_millis` to narrow results to a specific time window.\n\n\n\n\n#### Endpoint URL\n"
      tags:
      - 26.4.0.cl
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SearchChannelHistoryRequest'
        required: true
      parameters: []
      responses:
        '200':
          description: Channel status logs retrieved successfully.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SearchChannelHistoryResponse'
              examples:
                example_1:
                  description: Search webhook channel history by channel identifier and event
                  value:
                    jobs:
                    - id: n.6170538a-a4d4-4712-91bf-39b353db2b72
                      status: SUCCESS
                      creation_time_in_millis: 1771599720674
                      event:
                        type: LIVEBOARD_SCHEDULE
                        id: 2bb2ff83-b8d9-4d2b-8913-b2589bb6831b
                        name: schedule-identifier
                        run_id: 90c4f1b0-08c9-4a6c-8e61-49cffd9f1550
                      recipients:
                      - type: USER
                        id: d211f619-8b72-45d3-92a7-69dde41159c7
                        name: admin-user
                        email: admin@example.com
                      detail: ''
                      try_count: 1
                    - id: n.5c5bbedb-c425-48c0-8b54-a17267b08e7c
                      status: SUCCESS
                      creation_time_in_millis: 1771599600508
                      event:
                        type: LIVEBOARD_SCHEDULE
                        id: 2bb2ff83-b8d9-4d2b-8913-b2589bb6831b
                        name: schedule-identifier
                        run_id: b9834966-fe85-4fa9-8a10-9889c01d4826
                      recipients:
                      - type: USER
                        id: d211f619-8b72-45d3-92a7-69dde41159c7
                        name: admin-user
                        email: admin@example.com
                      detail: ''
                      try_count: 1
                example_2:
                  description: Search webhook channel history by job ID
                  value:
                    jobs:
                    - id: n.5c5bbedb-c425-48c0-8b54-a17267b08e7c
                      status: SUCCESS
                      creation_time_in_millis: 1771599600508
                      event:
                        type: LIVEBOARD_SCHEDULE
                        id: 2bb2ff83-b8d9-4d2b-8913-b2589bb6831b
                        name: schedule-identifier
                        run_id: b9834966-fe85-4fa9-8a10-9889c01d4826
                      recipients:
                      - type: USER
                        id: d211f619-8b72-45d3-92a7-69dde41159c7
                        name: admin-user
                        email: admin@example.com
                      detail: ''
                      try_count: 1
        '400':
          description: Invalid request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                invalid_request:
                  summary: Invalid request
                  value:
                    error:
                      message:
                        code: 10002
                        incident_id_guid: a1b2c3d4-e5f6-7890-abcd-ef1234567890
                        trace_id_guid: a1b2c3d4-e5f6-7890-abcd-ef1234567890
                        debug: channel_type must be specified. Currently only WEBHOOK is supported.
        '401':
          description: Unauthorized access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                unauthorized_access:
                  summary: Unauthorized access
                  value:
                    error:
                      message:
                        code: 10097
                        incident_id_guid: b2c3d4e5-f678-9012-bcde-f23456789012
                        trace_id_guid: b2c3d4e5-f678-9012-bcde-f23456789012
                        debug: Authentication required to retrieve channel delivery history.
        '403':
          description: Forbidden access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                forbidden_access:
                  summary: Forbidden access
                  value:
                    error:
                      message:
                        code: 10023
                        incident_id_guid: c3d4e5f6-7890-1234-cdef-345678901234
                        trace_id_guid: c3d4e5f6-7890-1234-cdef-345678901234
                        debug: Insufficient privileges to retrieve channel delivery history.
        '500':
          description: Unexpected error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                unexpected_error:
                  summary: Unexpected error
                  value:
                    error:
                      message:
                        code: 10038
                        incident_id_guid: d4e5f678-9012-3456-defa-456789012345
                        trace_id_guid: d4e5f678-9012-3456-defa-456789012345
                        debug: Unexpected server error while retrieving channel delivery history.
  /api/rest/2.0/system/communication-channels/validate:
    post:
      operationId: validateCommunicationChannel
      description: '

        <span class="since-beta-tag">Beta</span> <span class="since-beta-tag">Version: 26.4.0.cl or later</span>


        Validates a communication channel configuration to ensure it is properly set up and can receive events.

        - Use `channel_type` to specify the type of communication channel to validate (e.g., WEBHOOK).

        - Use `channel_identifier` to provide the unique identifier or name for the communication channel.

        - Use `event_type` to specify the event type to validate for this channel.


        Requires `ADMINISTRATION` (**Can administer ThoughtSpot**) or `DEVELOPER` (**Has developer privilege**) privilege. For webhook channels, users with `CAN_MANAGE_WEBHOOKS` (**Can manage webhooks**) privilege are also authorized to perform this action.





        #### Endpoint URL

        '
      tags:
      - 26.4.0.cl
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ValidateCommunicationChannelRequest'
        required: true
      parameters: []
      responses:
        '200':
          description: communication channel configuration validated successfully.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CommunicationChannelValidateResponse'
              examples:
                example_1:
                  description: Successful webhook validation with HTTP check only
                  value:
                    channel_type: WEBHOOK
                    channel_id: f47ac10b-58cc-4372-a567-0e02b2c3d479
                    channel_name: My Liveboard Webhook
                    event_type: LIVEBOARD_SCHEDULE
                    job_id: 9a8b7c6d-5e4f-3210-fedc-ba9876543210
                    result_code: SUCCESS
                    details:
                    - validation_step: HTTP_CONNECTION_CHECK
                      status: SUCCESS
                      http_status: 200
                      error_message: null
                      aws_s3_info: null
                example_2:
                  description: Successful webhook validation with both HTTP and S3 storage checks
                  value:
                    channel_type: WEBHOOK
                    channel_id: a1b2c3d4-e5f6-7890-abcd-ef1234567890
                    channel_name: S3 Storage Webhook
                    event_type: LIVEBOARD_SCHEDULE
                    job_id: b2c3d4e5-f678-9012-bcde-f23456789012
                    result_code: SUCCESS
                    details:
                    - validation_step: HTTP_CONNECTION_CHECK
                      status: SUCCESS
                      http_status: 200
                      error_message: null
                      aws_s3_info: null
                    - validation_step: STORAGE_FILE_UPLOAD_CHECK
                      status: SUCCESS
                      http_status: null
                      error_message: null
                      aws_s3_info:
                        bucket_name: my-webhook-files
                        file_name: thoughtspot-validation-test.json
                        object_key: webhooks/thoughtspot-validation-test.json
                example_3:
                  description: 'Partial success: HTTP check passed but S3 upload failed'
                  value:
                    channel_type: WEBHOOK
                    channel_id: c3d4e5f6-7890-1234-cdef-345678901234
                    channel_name: Failed S3 Webhook
                    event_type: LIVEBOARD_SCHEDULE
                    job_id: d4e5f678-9012-3456-defa-456789012345
                    result_code: PARTIAL_SUCCESS
                    details:
                    - validation_step: HTTP_CONNECTION_CHECK
                      status: SUCCESS
                      http_status: 200
                      error_message: null
                      aws_s3_info: null
                    - validation_step: STORAGE_FILE_UPLOAD_CHECK
                      status: FAILED
                      http_status: null
                      error_message: Access denied. Ensure the IAM role has s3:PutObject permission on the target bucket.
                      aws_s3_info: null
        '400':
          description: Invalid request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                invalid_request:
                  summary: Invalid request
                  value:
                    error:
                      message:
                        code: 10002
                        incident_id_guid: a1b2c3d4-e5f6-7890-abcd-ef1234567890
                        trace_id_guid: a1b2c3d4-e5f6-7890-abcd-ef1234567890
                        debug: Webhook with the specified channel_identifier was not found.
        '401':
          description: Unauthorized access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                unauthorized_access:
                  summary: Unauthorized access
                  value:
                    error:
                      message:
                        code: 10097
                        incident_id_guid: b2c3d4e5-f678-9012-bcde-f23456789012
                        trace_id_guid: b2c3d4e5-f678-9012-bcde-f23456789012
                        debug: Authentication required to validate a communication channel.
        '403':
          description: Forbidden access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                forbidden_access:
                  summary: Forbidden access
                  value:
                    error:
                      message:
                        code: 10023
                        incident_id_guid: c3d4e5f6-7890-1234-cdef-345678901234
                        trace_id_guid: c3d4e5f6-7890-1234-cdef-345678901234
                        debug: Insufficient privileges to validate communication channels.
        '500':
          description: Unexpected error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                unexpected_error:
                  summary: Unexpected error
                  value:
                    error:
                      message:
                        code: 10038
                        incident_id_guid: d4e5f678-9012-3456-defa-456789012345
                        trace_id_guid: d4e5f678-9012-3456-defa-456789012345
                        debug: Unexpected server error while validating the communication channel.
  /api/rest/2.0/template/variables/create:
    post:
      operationId: createVariable
      description: '

        Create a variable which can be used for parameterizing metadata objects <br/>  <span class="since-beta-tag">Version: 26.4.0.cl or later</span>


        Allows creating a variable which can be used for parameterizing metadata objects in ThoughtSpot.


        Requires ADMINISTRATION role and TENANT scope.

        The CAN_MANAGE_VARIABLES permission allows you to manage Formula Variables in the current organization scope.


        The API endpoint supports the following types of variables:

        * CONNECTION_PROPERTY - For connection properties

        * TABLE_MAPPING - For table mappings

        * CONNECTION_PROPERTY_PER_PRINCIPAL - For connection properties per principal. In order to use this please contact support to enable this.

        * FORMULA_VARIABLE - For Formula variables, introduced in 10.15.0.cl


        When creating a variable, you need to specify:

        * The variable type

        * A unique name for the variable

        * Whether the variable contains sensitive values (defaults to false)

        * The data type of the variable, only specify for formula variables (defaults to null)


        The operation will fail if:

        * The user lacks required permissions

        * The variable name already exists

        * The variable type is invalid




        #### Endpoint URL

        '
      tags:
      - 26.4.0.cl
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateVariableRequest'
        required: true
      parameters: []
      responses:
        '200':
          description: Create variable is successful.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Variable'
        '400':
          description: Invalid request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Unexpected error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
  /api/rest/2.0/template/variables/delete:
    post:
      operationId: deleteVariables
      description: '

        Delete variable(s) <br/>  <span class="since-beta-tag">Version: 26.4.0.cl or later</span>


        Allows deleting multiple variables from ThoughtSpot.


        Requires ADMINISTRATION role and TENANT scope.

        The CAN_MANAGE_VARIABLES permission allows you to manage Formula Variables in the current organization scope.


        The API endpoint requires:

        * The variable identifiers (IDs or names)


        The operation will fail if:

        * The user lacks required permissions

        * Any of the variables don''t exist

        * Any of the variables are being used by other objects





        #### Endpoint URL

        '
      tags:
      - 26.4.0.cl
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/DeleteVariablesRequest'
        required: true
      parameters: []
      responses:
        '204':
          description: Deletion of variable(s) is successful.
        '400':
          description: Invalid request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Unexpected error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
  /api/rest/2.0/template/variables/{identifier}/update-values:
    post:
      operationId: putVariableValues
      description: '

        Update values for a variable <br/>  <span class="since-beta-tag">Version: 26.4.0.cl or later</span>


        Allows updating values for a specific variable in ThoughtSpot.


        Requires ADMINISTRATION role.

        The CAN_MANAGE_VARIABLES permission allows you to manage Formula Variables in the current organization scope.


        The API endpoint allows:

        * Adding new values to the variable

        * Replacing existing values

        * Deleting values from the variable

        * Resetting all values


        When updating variable values, you need to specify:

        * The variable identifier (ID or name)

        * The values to add/replace/remove

        * The operation to perform (ADD, REPLACE, REMOVE, RESET)


        Behaviour based on operation type:

        * ADD - Adds values to the variable if this is a list type variable, else same as replace.

        * REPLACE - Replaces all values of a given set of constraints with the current set of values.

        * REMOVE - Removes any values which match the set of conditions of the variables if this is a list type variable, else clears value.

        * RESET - Removes all constraints for the given variable, scope is ignored





        #### Endpoint URL

        '
      tags:
      - 26.4.0.cl
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PutVariableValuesRequest'
        required: true
      parameters:
      - in: path
        name: identifier
        required: true
        schema:
          type: string
        description: Unique ID or name of the variable
      responses:
        '204':
          description: Variable values updated successfully.
        '400':
          description: Invalid request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Unexpected error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
  /api/rest/2.0/template/variables/search:
    post:
      operationId: searchVariables
      description: '

        Search variables <br/>  <span class="since-beta-tag">Version: 26.4.0.cl or later</span>


        Allows searching for variables in ThoughtSpot.


        Requires ADMINISTRATION role.

        The CAN_MANAGE_VARIABLES permission allows you to manage Formula Variables in the current organization scope.


        The API endpoint supports searching variables by:

        * Variable identifier (ID or name)

        * Variable type

        * Name pattern (case-insensitive, supports % for wildcard)


        The search results can be formatted in three ways:

        * METADATA - Returns only variable metadata (default)

        * METADATA_AND_VALUES - Returns variable metadata and values


        The values can be filtered by scope:

        * org_identifier

        * principal_identifier

        * model_identifier





        #### Endpoint URL

        '
      tags:
      - 26.4.0.cl
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SearchVariablesRequest'
        required: true
      parameters: []
      responses:
        '200':
          description: List of variables is successful.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Variable'
        '400':
          description: Invalid request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Unexpected error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
  /api/rest/2.0/template/variables/{identifier}/update:
    post:
      operationId: updateVariable
      description: '

        Update a variable''s 

# --- truncated at 32 KB (62 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/thoughtspot/refs/heads/main/openapi/thoughtspot-26-4-0-cl-api-openapi.yml