I am using HTTP request activity & passed the required values like the URL. The Api key is passed in the header.
I have passed the same data in Postman; it’s working and giving the status Code 200 OK But in UiPath getting this error. Could you please help in identifying this issue.
@nithya A 503 Service Unavailable usually means the server is reachable, but it is not able to process the request from UiPath at that moment. Since the same call works in Postman, the issue is most likely with how the request is being sent from UiPath.
→ For a GET request, usually you should not send a body
→ Compare the exact headers from Postman and UiPath, especially Authorization/API key, Content-Type, Accept, and User-Agent
→ If Postman is using query parameters, make sure they are passed the same way in UiPath
→ From the screenshot, one thing that stands out is that the request method is GET but the body type is set as Text / text/xml. If the API is a GET call, try removing the body completely and pass only the required headers/parameters.
@nithya If the request is working in Postman, could you try exporting it as cURL from Postman and importing that into the UiPath HTTP Request activity? That is usually the easiest way to make sure the UiPath request matches Postman exactly, especially for headers, authentication format, and other request details that Postman may be adding automatically.
From the impacted Studio machine, provide a screenshot from the PowerShell_ISE.exe while you are running the below script. It will tell you which is the default browser in the system. You need to have Edge/Chrome/Firefox as the default browser.
Note: Firefox has a different configuration, where you can use completely different proxy details from your system. That should be checked separately.
Note:
If the AbsoluteUri value is different from the targeted URL, that means that is the proxy address that you need to specify in the HTTP Request.
If the AbsoluteUri value has the same value as the targeted URL (https://maxifleet.komatsuforest.com:600), that means in the HTTP Request you need to bypass that URL from your proxy server.
Such scenarios are hard to diagnose without root cause analysis and Postman usually does some implicit configurations related to the machine it’s running on.
I strongly recommend using the activity’s Enable debugging info under Response options section. This will enrich the response you get in the Report text box and will also add it to the httpResponse.RawDebugginInfo property of the Output.
The information is structured for LLM consumption, therefore Claude or Autopilot can easily help debug what’s happening. Just make sure that you don’t expose secrets you don’t want to. Sensitive information sterilization exists but it’s not exhaustive.