[DOCS]: API Documentation Missing Content

[pop9s]

Type of Documentation Change

Content update

Documentation Page URL or Path

https://docs.dify.ai/api-reference

Current Content

API Documentation Missing Content

Suggested Changes

The following interfaces are used in practice but not documented:
Datasets module:
GET console/api/datasets/{id}/error-docs
GET console/api/datasets/{id}/metadata
GET console/api/datasets/{id}/related-apps
GET console/api/datasets/{id}/use-check
Explore module:
GET console/api/explore/apps
Features module:
GET console/api/features
Files module:
GET console/api/files/support-type
Apps module:
GET console/api/apps/imports/{uuid}/check-dependencies
GET console/api/apps/{id}/advanced-chat/workflow-runs
GET console/api/apps/{id}/workflows/default-workflow-block-configs
GET console/api/apps/{id}/api-keys
GET console/api/apps/{id}/text-to-audio/voices
GET console/api/apps/{id}/workflows/draft
GET console/api/apps/{id}/workflows/draft/config
GET console/api/apps/{id}/workflows/draft/conversation-variables
GET console/api/apps/{id}/workflows/draft/system-variables
GET console/api/apps/{id}/workflows/publish
GET console/api/apps/{id}/workflows/draft/variables
GET api/webapp/access-mode
GET console/api/account/profile

Reason for Change

A large number of Console-related API interfaces and URL splicing rules are missing from the documentation, and the description of public variables is incomplete

Code of Conduct

• I agree to follow Dify's documentation contribution guidelines
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

[hsiong]

Related / similar: #540 (API docs discoverability gap)

• ✅ Document metadata assignment API is documented under “Use Dify”:
  https://docs.dify.ai/en/use-dify/knowledge/manage-knowledge/maintain-dataset-via-api#modify-metadata-for-a-single-document-assignment

• ❌ But it’s not referenced in the API Reference “Knowledge → Documents” section (example page):
  https://docs.dify.ai/api-reference/documents/create-a-document-from-text

Impact

• If someone reads only API Reference, it’s easy to assume the metadata assignment endpoint doesn’t exist.

Suggestion (low effort)

• Add a short “See also / Related endpoints” note in API Reference → Documents pages linking to:
  • dataset metadata fields endpoints
  • document metadata assignment endpoint
    (cross-link only, no need to duplicate full content)

Expectation

• Would love to see this cross-link added so API Reference users can find the metadata workflow without jumping between sections.

[RiskeyL]

Hi @hsiong @pop9s, thank you for bringing this up. Due to some legacy reasons, our API reference has been out of sync with the code and has some gaps. We're currently working on a solution for batch updates, after which the content under "Use Dify" will be removed to make the API reference the single source of truth. I'll share updates with you here as we make progress.