[Question]: HTTP API-list chunks cannot get chunks in Markdown files

[Kevinona]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (Language Policy).
• Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
• Please do not modify this template :) and fill in all the required fields.

Describe your problem

I want to use list chunks method to get chunks down the document. And the type of document is markdown.
So I use the command below, but the response dose not contains any chunks.
curl --request GET \ --url http://{address}/api/v1/datasets/{dataset_id}/documents/{document_id}/chunks --header 'Authorization: Bearer <YOUR_API_KEY>'

response:

The chunks list is empty. But in doc, "chunk_count": 5. And I can see those chunks in the front end. those chunks are enabled.

However, if the type is pdf. The api works.

[dosubot]

Hi @Kevinona! I'm Dosu and I’m helping the ragflow team.

This is a known issue: the API endpoint for listing chunks checks if the backend chunk store index exists for the dataset and tenant before returning results. If this check fails (which can happen for Markdown documents due to index naming or creation mismatches), the API returns an empty chunk list—even if chunks exist and are visible in the frontend. The frontend may bypass this check or use a different retrieval path, which is why you still see the chunks there. There is no special logic in the API for Markdown vs PDF; the difference is likely due to how the index existence is validated or named for Markdown uploads. No merged PRs currently fix this for Markdown files as of December 2025. For now, verifying the index existence and ensuring consistent naming/creation for Markdown documents may help align API and frontend behavior. More details: API implementation, backend logic, known issue reference.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[KevinHuSh]

I doubt that either dataset_id or document_id is not correct.