How to pass data to an API one by one and store the responses

Need help APIs
1

I have an api which give data on response when we upload an image to it
my appliction have to perform and upload multiple images and the api only take one at a time
i have to pass all the image one by one in the api till i pass all the image from the list of image i have stored
i will then have to pass to another api after that where it takes array of response from each image upload
i want help in how can i store response of each image upload till all the image uploaded in between then utilzie in the final api

2

You can use Schedule api workflow on a list (type image) and run the API call in this backend WF

3

I want to store each response again in a list then I want to then use all of the response for each image to another api at once
How to store those responses

4

Just schedule another wf on a list (type of the API response?). Not sure to understand exactly what is your process.

5

I have two APIs first api is to upload image it only accept one image at a time and it return response like image url and original name and all the fields for the image after uploading to the api

Now there is another api which creates a product and in that api there is parameter which is array of those Responses and the user can upload multiple images in a product and in final api where product is uploaded we have to give all the response of all the image which we uploaded through the previous image upload api

This is the case if you could understand

6

This is exactly what I tell you
First Schedule on a list of image, from this WF, after the API response, Schedule on a list of the type of the API Response list (I don’t know the name, but you can see it in API Connector when you initialize your call)

If you need to merge them all in a single item, you may need to check to have enough time between each schedule on a list to avoid racing issue. But in most case, you will probably create one response for each image/array list item. You only need to have something to link them together (user or DB thing for example). This information should be provided in the first Backend WF in a parameters that will also be used in the second Backend WF when you schedule on a list.