Hello everyone,
I noticed that there are three different HTTP Request activities available for making API calls. In one of my agentic projects, I have used the HTTP Request (Legacy) activity. I am concerned about whether this activity might be deprecated in the future.
There is no clear deprecation planned yet but it’s better to start using the newer HTTP Request for the new developments.
You can keep eye on the deprecation timeline time to time to get the timeline of future deprecations
The advice from UiPath is to start using the new HTTP Request activity.
You can read more about it here:
Do you experience any issues when migrating/switching activities?
Or is it just that it can be cumbersome to manually switch them all?
Regards
Soren
This is correct, because it’s just better (and we’re actively spotting and fixing any edge case issues our users report to make it even more resilient). There are not many such reports, which is a really good sign.
Just to clarify: even if we decide to finally hide the legacy activity from search, it will happen in multiple stages with enough heads-up. The first step would theoretically be to hide it from search, but even then it would still remain available in the package code so that existing projects don’t immediately break.
Even after we decide to remove it from the code altogether (mostly driven by our desire to drop RestSharp as a dependency of the WebAPI package), you could still use the older (last) version of the WebAPI package that supported the legacy activity.
I hope all this context helps you decide which activity to use in your new projects 
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
