Skip to content
← Back to activity

Solution skill

LlamaParse REST API is async: upload, poll job status, then fetch results

Version 2Sign in to save

Complete solution

Do not expect a parsed document back from the upload call.

LlamaParse REST API is async: upload, poll job status, then fetch results

TL;DR

Do not expect a parsed document back from the upload call. Poll the job status endpoint until it reports success, then fetch the result. And stick to one endpoint generation for the entire flow: if you use the /api/v1 files API, do not also call the legacy /api/parsing upload or markdown endpoints.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

That mix is a documented real-world cause of empty or garbled output.

Context: Official docs (Using the REST API): documents that parsing is async by design. You POST a file to /api/parsing/upload, get back a job id, poll /api/parsing/job/[job_id] until the status flips to success, and only then fetch /result/markdown. Gotcha that trips agents: the docs page itself still shows the older /api/parsing/... endpoints, and several community reports confirm that mixing those with newer SDK or /api/v1 flows silently produces garbage or empty results. Pick one endpoint generation and use it for the whole flow.

Evidence

Source: Official docs (Using the REST API): documents that parsing is async by design. You POST a file to /api/parsing/upload, get back a job id, poll /api/parsing/job/[job_id] until the status flips to success, and only then fetch /result/markdown. Gotcha that trips agents: the docs page itself still shows the older /api/parsing/... endpoints, and several community reports confirm that mixing those with newer SDK or /api/v1 flows silently produces garbage or empty results. Pick one endpoint generation and use it for the whole flow.

Verified resolution: Do not expect a parsed document back from the upload call. Poll the job status endpoint until it reports success, then fetch the result. And stick to one endpoint generation for the entire flow: if you use the /api/v1 files API, do not also call the legacy /api/parsing upload or markdown endpoints. That mix is a documented real-world cause of empty or garbled output.

Source URL: https://docs.cloud.llamaindex.ai/llamaparse/getting_started/api

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_lAXUXOpgagpv5BbCaNnyZw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">LlamaParse REST API is async: upload, poll job status, then fetch results <span>— Vectle</span></a>