cancel
Showing results for 
Search instead for 
Did you mean: 

multiple HTTP connection endpoints within 1 recipe

shruti-2-sharma
Deputy Chef I
Deputy Chef I

I am trying to create recipe to call more than 1 http connector.

But facing issue while using multiple HTTP connection endpoints within 1 recipe.

only one connection work at a time.

please suggest me how to do it.

Thanks in advance

1 ACCEPTED SOLUTION

max-knutsson
Workato employee
Workato employee

So all of these are totally different systems/APIs?

If answer is Yes, then I see 2 options

1. Use a callable function (go to next step => search callable recipe by workato) because if using callable function you will not hit the HTTP connector limit, basically you can have as many callables as you want.

a) Create a callable function for API 1 - use whatever authentication method required for this API, create parameters that you need to push to this callable recipe, call the API then return the result back to the MAIN recipe

b) repeat the same steps 4 more times until you have 5 callable functions, each calling their own api, accepting their own Parameters and return Result


2. Second option is to use HTTP to 5 different APIs but create a "generic" http connector which has "Authentication" NONE and authentication using HTTP headers manually for each call. This will be messy as its not very reusable. For reusability/Best practice I recommend option 1, use this option only as last resort, as pointed out by Joseph above.






View solution in original post

11 REPLIES 11

rayudu_addagarl
Deputy Chef I
Deputy Chef I

Another option of your API supports graphql , and its same system one could get better results without multiple calls to end points.


As always there are tradeoffs of usine one vs other


Since GraphQL substantially reduces the number of endpoints, services can acquire all the needed data with one call and can format this information inJSONfor fast retrieval. GraphQL is alsotransport-layeragnostic, so the API server can exchange data over any protocol, including HTTP, HTTPS and WebSockets, and TCP.

A head-to-head GraphQL vs. REST performance faceoff (techtarget.com)

levajar
Deputy Chef II
Deputy Chef II

Love this community discussions with ideas of calling multiple http endpoints within a single recipe. 

If we have someone built a community recipe template - probably that will add more value as well for folks to refer it.