1
A way to capture and process Async responses?
Source: Kong/insomnia#6514 · opened by @davehouser1
my API works the following way:
• send a POST request. The API will do some basic tests and if they all pass return a 200 with a job id.
• The api backend will then do work and send out an async response when complete. The POST request has to include a "notification URL" of where my API can send back a the async response when the work is done.
Is there a way in insomnia to not only check the response back form sending the api, but also capture the async response and analyze it? My plan is to put the Insomnia host ip and port as the async response url in my initial POST, then have insomnia capture the response an analyze.
I am aware this is not a good way to manage / process status of a job. I know a message bus is in order, but this is outside of what I have control of. I did not develop this data flow, its how the system works unfortunately.
Anyway to do this?
• send a POST request. The API will do some basic tests and if they all pass return a 200 with a job id.
• The api backend will then do work and send out an async response when complete. The POST request has to include a "notification URL" of where my API can send back a the async response when the work is done.
Is there a way in insomnia to not only check the response back form sending the api, but also capture the async response and analyze it? My plan is to put the Insomnia host ip and port as the async response url in my initial POST, then have insomnia capture the response an analyze.
I am aware this is not a good way to manage / process status of a job. I know a message bus is in order, but this is outside of what I have control of. I did not develop this data flow, its how the system works unfortunately.
Anyway to do this?
No pledges yet. Be the first to back this.
Comments
Similar requests
How to avoid Error: failed to find workspace while running inso CLI?
1 vote · 0 comments
Ability to sync responses history
1 vote · 0 comments
Example support for requests
3 votes · 0 comments
Add "diff" feature to Response History
4 votes · 0 comments
Expose electron.clipboard.writeHTML to context.app.clipboard
1 vote · 0 comments
No comments yet.