Batch GET requests

We have purposely not supported sending multiple requests with other methods in one execution since this would cause problems if some of the requests fail while others worked. The only exception are GET requests.
If you want to send several requests using another method than GET in a row we recommend to use a loop. Alternatively, the RESTful service you are interacting with might support fetching a selected subset of a collection resource with a single GET request (everest provides a custom query language for this purpose).

If you want to sent multiple GET requests in one node execution you have to use the GET Resource (Batch) node. It works very similar to the normal GET Resource node (see Step 1) except for 3 details:

  1. It only accepts URL input via column (see Step 4). Unlike as in the normal node, the URLs in the table might be different.
    URL selection in a batch GET node
  2. There is only one output table that presents the request URL and the status code, content type and body of the response for the request. There is no detailed header data.
    Batch GET node output table
  3. There is no view presenting the response bodies.

Like in a normal GET resource node you can predict of the representation column in the output table. However, if there is a mixture of XML-like and non-XML-like representations the node will always use a string cell.

Conversion of the representation works via the normal Read REST representation node (see Step 2). If you want to use the data format autodection connect the output table of the GET resource (Batch) node to both input porte of the converter node. The Read REST representation summarizes the data of all representations in output table.
This output table will contain all data of all representations. If there is a resource value missing in one representation, the referring cell will be left empty.
It is allowed to combine different input data formats.

Tutorial worklist including batch GET node