Multiple Requests

Making multiple requests is easy - you just have to put all your request objects in an array. All requests will be executed sequentially and the output of the last request will be used as the module’s output.

During the execution of multiple calls in a module, when the service returns an HTTP error, it is not possible to evaluate it as a success. Therefore, handling the error by e. g. another call is not possible.

Examples of Multiple Requests

Extending Data by Executing Additional Call

[
    {
        "url": "http://example.com/api/user",
        "response": {
            "temp": {
                "username": "{{body.username}}"
            }
        }    
    },
    {
        "url": "http://example.com/items",
        "response": {
            "iterate": "{{body}}",
            "output": {
                "username": "{{temp.username}}",
                "text": "{{item.text}}"
            }
        }
    }
]

Handling of Full Update Approach

When the endpoint for updating a record has a full update approach, where in order to update a record correctly, you need to provide all parameters. If some parameters are omitted, they will be cleared or overridden to default values. Since it is extremely user-unfriendly, you need to handle it on the app's side.

pageUpdate modules

Handling of Asynchronous Approach

When a web service doesn't support a synchronous approach and the common use case of the module requires support, it should be added on the app's side.

pageAction modules