> ## 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 Tables

> Lists all [Peaka Tables](https://docs.peaka.com/connecting-your-data/peaka-table) in the project. Peaka Table is an internal relational database within Peaka that allows you to organize and manage data efficiently. It supports structured data storage and enables you to add, delete, filter, and edit your data, including JSON data types. It is best suited for smaller datasets requiring frequent edits and broader data type support. See also: [Differences of Peaka Table and Peaka BI Table](https://docs.peaka.com/connecting-your-data/differences-of-peaka-table-and-peaka-bi-table)

<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}/table
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}/table:
    get:
      tags:
        - Data -- Internal Tables
      summary: List Tables
      description: >-
        Lists all [Peaka
        Tables](https://docs.peaka.com/connecting-your-data/peaka-table) in the
        project. Peaka Table is an internal relational database within Peaka
        that allows you to organize and manage data efficiently. It supports
        structured data storage and enables you to add, delete, filter, and edit
        your data, including JSON data types. It is best suited for smaller
        datasets requiring frequent edits and broader data type support. See
        also: [Differences of Peaka Table and Peaka BI
        Table](https://docs.peaka.com/connecting-your-data/differences-of-peaka-table-and-peaka-bi-table)
      operationId: listTables
      parameters:
        - name: projectId
          in: path
          description: ID of the Project
          required: true
          schema:
            type: string
          example: mtKDhe1U
      responses:
        '200':
          description: OK
          content:
            '*/*':
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Table'
components:
  schemas:
    Table:
      type: object
      properties:
        catalogId:
          type: string
          description: The ID of the catalog that the table belongs to.
        catalogName:
          type: string
          description: The name of the catalog that the table belongs to.
        schemaName:
          type: string
          description: The name of the schema that the table belongs to.
        tableName:
          type: string
          description: The name of the table.
        isCacheable:
          type: boolean
          description: Indicates whether the table is cacheable or not.
        isDynamicTable:
          type: boolean
          description: >-
            Indicates whether the table has required query parameter columns or
            not.
             A query parameter column is prefixed with "_q_" e.g. "_q_date".
             These columns are used to filter the data in the table.
        isCached:
          type: boolean
          description: |-
            Indicates whether the table is cached or not.
             It is not the status of caching.
             <br>
             e.g. when a table is cached, you are no longer accessing the original data source.
             But the data may not be complete since an ongoing cache refresh is in progress.
      description: Represents a table in a schema.
  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

````