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

# List Queries

> Returns all queries belonging to the given project. Each query includes its path and folderId if it is placed in a folder.

<span style={{display: "flex", gap: "10px", flexDirection: "row", alignItems: "center"}}>
  <img src="https://cdn.peaka.com/badges/partner-api-key-badge.png" />

  <img src="https://cdn.peaka.com/badges/project-api-key-badge.png" />
</span>


## OpenAPI

````yaml get /data/projects/{projectId}/queries
openapi: 3.0.1
info:
  title: Peaka Gateway API
  description: Peaka Gateway API Documentation
  version: '1.0'
servers:
  - url: https://partner.peaka.studio/api/v1
    description: Default Server URL (US Zone)
  - url: https://partner.eu.peaka.studio/api/v1
    description: EU Zone
security:
  - bearerAuth: []
paths:
  /data/projects/{projectId}/queries:
    get:
      tags:
        - Data -- Queries
      summary: List Queries
      description: >-
        Returns all queries belonging to the given project. Each query includes
        its path and folderId if it is placed in a folder.
      operationId: listQueries
      parameters:
        - name: projectId
          in: path
          description: ID of the Project
          required: true
          schema:
            type: string
          example: mtKDhe1U
      responses:
        '200':
          description: List of queries
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Query'
              example:
                - id: '709891320440684892'
                  displayName: sample2
                  name: sample2
                  inputQuery: ''
                  path: /reports/monthly
                  folderId: f_3np1a
                - id: '702142445051183684'
                  displayName: deneme
                  name: deneme
                  inputQuery: >-
                    SELECT count(*) from
                    "examplestripecatalogname"."payment"."customers"
                - id: '709891051854233848'
                  displayName: sample
                  name: sample
                  inputQuery: ''
                  path: /reports/monthly
                  folderId: f_3np1a
                - id: '709922802836177297'
                  displayName: sampleQuery
                  name: samplequery
                  inputQuery: SELECT * from "mycatalog".payment.charges
                - id: '709922802836177298'
                  displayName: dailyRevenue
                  name: dailyrevenue
                  inputQuery: SELECT * from "mycatalog".payment.charges
                  queryType: MATERIALIZED
                  schedule:
                    type: cron
                    cronExpression: 0 0 * * *
                    timezone: UTC
components:
  schemas:
    Query:
      type: object
      properties:
        id:
          type: string
          description: The ID of the query.
        displayName:
          type: string
          description: The display name of the query.
        name:
          type: string
          description: >-
            The name of the query used in SQL, e.g. SELECT * FROM
            "peaka"."query"."<name>". For a MATERIALIZED query the materialized
            result is queryable as "peaka"."mtquery"."<name>".
        inputQuery:
          type: string
          description: >-
            The SQL query. For a materialized query created from an existing
            query (via inputQueryRefId), this holds the snapshot of the source
            query's SQL resolved when the query was created or last updated with
            the reference.
        queryType:
          type: string
          description: The type of the query.
          enum:
            - PLAIN
            - MATERIALIZED
        schedule:
          $ref: '#/components/schemas/MaterializedQuerySchedule'
        path:
          type: string
          description: >-
            The folder path of the query (e.g. "/analytics/dashboards"). Null if
            not in any folder.
          nullable: true
        folderId:
          type: string
          description: >-
            The ID of the folder containing this query. Null if not in any
            folder.
          nullable: true
      description: A saved query belonging to a project.
    MaterializedQuerySchedule:
      type: object
      properties:
        type:
          type: string
          description: Type of schedule.
          enum:
            - interval
            - cron
            - none
        cronExpression:
          type: string
          description: >-
            UNIX cron expression (minute hour day-of-month month day-of-week),
            e.g. '0 0 * * *' for every day at midnight. Set only when the
            schedule type is 'cron'.
          nullable: true
          example: 0 0 * * *
        repeatDuration:
          type: string
          description: >-
            ISO-8601 duration between refreshes, e.g. 'PT6H' (every 6 hours),
            'PT12H' (twice daily), 'P1D' (daily). Set only when the schedule
            type is 'interval'.
          nullable: true
          example: PT12H
        timezone:
          type: string
          description: >-
            IANA timezone used to evaluate the cron expression, e.g. 'UTC' or
            'Europe/Istanbul'. Set only when the schedule type is 'cron'.
          nullable: true
          example: UTC
      description: >-
        Schedule configuration of a materialized query. Provide EITHER an
        interval schedule (`type=interval` with `repeatDuration`) OR a cron
        schedule (`type=cron` with `cronExpression` and optional `timezone`).
        Use `type=none` for no schedule. The fields that do not apply to the
        chosen type are omitted.
      nullable: true
      example:
        type: cron
        cronExpression: 0 0 * * *
        timezone: UTC
  securitySchemes:
    bearerAuth:
      type: http
      description: >-
        Use the Authorization header with the value 'Bearer <apiKey>' to
        authenticate. Partner API Keys have full access; Project API Keys are
        limited to their project scope. Learn more:
        https://docs.peaka.com/api-reference/authentication
      scheme: bearer
      bearerFormat: Api Key

````