Docling-server and Task id

[Tonic867]

Hello all,

I'm very new to this but learning quickly and just have a question with regards to GET results. I'm using n8n and below is a copy of my curl that I'm using. When converting a document via http://localhost:5001/ui/ a Task id is created.

When I execute the below I get "Problem in node ‘HTTP Request‘ The resource you are requesting could not be found" but if I copy and paste the Task id from the Docling GUI I get the result. What would be the correct expression used where you don't have to manually copy and paste the Task id?

curl -X 'GET'
'http://localhost:5001/v1/result/{task_id}'
-H 'accept: application/json'
-H 'X-API-Key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'

Thanks in advance.

[dosubot[bot]]

Hi @Tonic867! I'm Dosu and I’m helping the docling team.

You don't need to manually copy and paste the Task id in n8n. When you submit a document for conversion using the async API endpoint (like POST /v1/convert/file/async or /v1/convert/source/async), the response includes a JSON object with a field called task_id. You can extract this task_id programmatically in n8n and use it in your next HTTP Request node to fetch the result.

Here's how you can set this up in n8n:

1. Use an HTTP Request node to submit your document to the async endpoint. The response will contain the task_id in the JSON body.
2. In your next HTTP Request node (to GET /v1/result/{task_id}), use an expression to reference the task_id from the previous node. For example, if your first node is called "Submit Document", you can use:

   http://localhost:5001/v1/result/{{$json["task_id"]}}
   

   This will automatically insert the correct Task id from the previous response.

The error you saw ("resource you are requesting could not be found") happens because the placeholder {task_id} is not being replaced with the actual value—n8n needs to reference the output of the previous node, not a literal string.

If you want to wait for the task to finish before fetching the result, you can add a loop or use the /v1/status/poll/{task_id} endpoint to check if the task is complete before making the GET request for the result.

This approach is supported by the Docling-server API design: the async endpoints return the Task id in the response, and you can use that id to fetch the result once processing is done (source, source).

To reply, just mention @dosu.

---

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

[Tonic867]

Hello @dosu,

Sorry for the late reply your suggestion worked thank you for the direction

[dosubot[bot]]

You're welcome! Happy to help. If you have any more questions or need further assistance, just let me know.

To reply, just mention @dosu.

---

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