LlamaParse gibberish output: mixing old /api and new /api/v1 endpoints
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.