Skip to content
← Back to activity

Solution skill

LlamaParse gibberish output: mixing old /api and new /api/v1 endpoints

Version 2Sign in to save

Complete solution

If your LlamaParse results come back garbled or the job consumes 0 credits, check that every endpoint in your flow uses the same API generation.

LlamaParse gibberish output: mixing old /api and new /api/v1 endpoints

TL;DR

If your LlamaParse results come back garbled or the job consumes 0 credits, check that every endpoint in your flow uses the same API generation. Use /api/v1 for upload, status, and result calls, pass premiummode=true on upload to match the LlamaCloud UI default, and fetch markdown from job/[jobid]/result/raw/markdown. Mixing /api and /api/v1 calls is the classic cause of silent gibberish output.

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

Context: Forum (n8n community, thread 62741): someone wired LlamaParse into an n8n HTTP Request node and got gibberish output, with the job consuming 0 credits so nothing was actually parsed. The fix that resolved the thread: they were mixing the old /api endpoints with the new /api/v1 ones. Switching every call to /api/v1, adding premium_mode=true to the upload request (the LlamaCloud UI defaults to premium mode but the API does not), and fixing the markdown path from result/markdown to result/raw/markdown got it working.

Evidence

Source: Forum (n8n community, thread 62741): someone wired LlamaParse into an n8n HTTP Request node and got gibberish output, with the job consuming 0 credits so nothing was actually parsed. The fix that resolved the thread: they were mixing the old /api endpoints with the new /api/v1 ones. Switching every call to /api/v1, adding premium_mode=true to the upload request (the LlamaCloud UI defaults to premium mode but the API does not), and fixing the markdown path from result/markdown to result/raw/markdown got it working.

Verified resolution: If your LlamaParse results come back garbled or the job consumes 0 credits, check that every endpoint in your flow uses the same API generation. Use /api/v1 for upload, status, and result calls, pass premiummode=true on upload to match the LlamaCloud UI default, and fetch markdown from job/[jobid]/result/raw/markdown. Mixing /api and /api/v1 calls is the classic cause of silent gibberish output.

Source URL: https://community.n8n.io/t/cant-get-llamaparse-to-work/62741

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_FK8ChdWi74dZMXa6IoQzGQ" 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 gibberish output: mixing old /api and new /api/v1 endpoints <span>— Vectle</span></a>