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

# List the request-template variables

> The placeholders a request template (url / query / headers / body of
any api stage) may reference, with a one-line description, an example
rendered value and the stages each one is valid in.

This is the same vocabulary the publish pipeline validates against, so
editors and coding assistants can offer exactly what the platform
accepts instead of copying a variable list that drifts. Anonymous, like
the manifest schema: a deployment-level constant with no caller data.



## OpenAPI

````yaml /jp/datahub/api/openapi.json get /v1/data-apps/template-variables
openapi: 3.1.0
info:
  title: DataHub API
  version: 0.2.0
  description: Public /v1 contract of Octoparse DataHub. Internal channels are excluded.
servers:
  - url: https://api-datahub.octoparse.com
security:
  - bearerAuth: []
tags:
  - name: Discovery
    description: >-
      Anonymous access: platform metadata (currency), data app search, detail
      and input contract, machine-readable manifest spec.
  - name: Publishing
    description: >-
      Self-service publishing channel (API Key auth), two-phase: validate first
      (validate / package, nothing persisted), then publish (POST /data-apps,
      the submission goes live as a new Release). api kind (declarative
      integration) becomes visible on publish; code kind (code package) returns
      202 and enters an async image build; once ready it is promoted to a
      Release, visible and runnable. Poll progress via GET
      /data-apps/{ref}/builds.
  - name: Runs & Results
    description: >-
      Start / query / cancel runs and read result records with pagination.
      Business inputs go in the request body; platform run options (wait,
      max_records) go in query parameters.
  - name: Datasets
    description: >-
      Metadata and record access for platform datasets (including seeded stock
      data).
  - name: Account
    description: Account info and cumulative usage for the current API Key.
  - name: Secrets
    description: >-
      CRUD for upstream credentials (environment entries referenced by manifest
      `runtime.env`). Plaintext is write-only: every read returns a mask.
paths:
  /v1/data-apps/template-variables:
    get:
      tags:
        - Discovery
      summary: List the request-template variables
      description: |-
        The placeholders a request template (url / query / headers / body of
        any api stage) may reference, with a one-line description, an example
        rendered value and the stages each one is valid in.

        This is the same vocabulary the publish pipeline validates against, so
        editors and coding assistants can offer exactly what the platform
        accepts instead of copying a variable list that drifts. Anonymous, like
        the manifest schema: a deployment-level constant with no caller data.
      operationId: get_template_variables_v1_data_apps_template_variables_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DataEnvelope_dict_str__Any__'
components:
  schemas:
    DataEnvelope_dict_str__Any__:
      properties:
        data:
          additionalProperties: true
          type: object
          title: Data
      type: object
      required:
        - data
      title: DataEnvelope[dict[str, Any]]
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: DataHub API Key

````