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

# Get Built-in Metadata Fields

> Returns the list of built-in metadata fields provided by the system (e.g., document type, source URL).



## OpenAPI

````yaml /en/api-reference/openapi_knowledge.json get /datasets/{dataset_id}/metadata/built-in
openapi: 3.0.1
info:
  title: Knowledge API
  description: >-
    API for managing knowledge bases, documents, chunks, metadata, and tags,
    including creation, retrieval, and configuration. **Note:** A single
    Knowledge Base API key has permission to operate on all visible knowledge
    bases under the same account. Please pay attention to data security.
  version: 1.0.0
servers:
  - url: '{apiBaseUrl}'
    description: The base URL for the Knowledge API.
    variables:
      apiBaseUrl:
        default: https://api.dify.ai/v1
        description: Actual base URL of the API
security:
  - ApiKeyAuth: []
tags:
  - name: Knowledge Bases
    description: >-
      Operations for managing knowledge bases, including creation,
      configuration, and retrieval.
  - name: Documents
    description: >-
      Operations for creating, updating, and managing documents within a
      knowledge base.
  - name: Chunks
    description: Operations for managing document chunks and child chunks.
  - name: Metadata
    description: >-
      Operations for managing knowledge base metadata fields and document
      metadata values.
  - name: Tags
    description: Operations for managing knowledge base tags and tag bindings.
  - name: Models
    description: Operations for retrieving available models.
  - name: Knowledge Pipeline
    description: >-
      Operations for managing and running knowledge pipelines, including
      datasource plugins and pipeline execution.
paths:
  /datasets/{dataset_id}/metadata/built-in:
    get:
      tags:
        - Metadata
      summary: Get Built-in Metadata Fields
      description: >-
        Returns the list of built-in metadata fields provided by the system
        (e.g., document type, source URL).
      operationId: getBuiltInMetadataFields
      parameters:
        - name: dataset_id
          in: path
          required: true
          schema:
            type: string
            format: uuid
          description: Knowledge base ID.
      responses:
        '200':
          description: Built-in metadata fields.
          content:
            application/json:
              schema:
                type: object
                properties:
                  fields:
                    type: array
                    description: List of system-provided metadata fields.
                    items:
                      type: object
                      properties:
                        name:
                          type: string
                          description: >-
                            Built-in field identifier. `document_name` for the
                            document title, `uploader` for the creator,
                            `upload_date` for creation time, `last_update_date`
                            for last modification time, `source` for the
                            document origin.
                        type:
                          type: string
                          description: >-
                            Field data type. `string` for text values, `time`
                            for date/time values.
              examples:
                success:
                  summary: Response Example
                  value:
                    fields:
                      - name: document_name
                        type: string
                      - name: uploader
                        type: string
                      - name: upload_date
                        type: time
                      - name: last_update_date
                        type: time
                      - name: source
                        type: string
components:
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      bearerFormat: API_KEY
      description: >-
        API Key authentication. For all API requests, include your API Key in
        the `Authorization` HTTP Header, prefixed with `Bearer `. Example:
        `Authorization: Bearer {API_KEY}`. **Strongly recommend storing your API
        Key on the server-side, not shared or stored on the client-side, to
        avoid possible API-Key leakage that can lead to serious consequences.**

````