POSTMAN "Invalid Documents" Error with POSTMAN API Key-Based POST Integration After Updating to UiPath.WebAPIActivity v2.3.2

Here’s a quick summary:

  • I’m using an API key for authentication (Postman → Profile → Settings → API Key).
  • The same configuration worked previously without any issues.
  • The error started appearing after updating to UiPath.WebAPIActivity v2.3.2 (latest version).
  • I’ve also noticed that Postman is now prompting for either a WSDL or REST API definition, which wasn’t required earlier.

I’d like to understand:

  • Has there been any change in how the WebAPIActivity handles API key authentication or document formatting?
  • Is there any updated documentation or migration guidance I might have missed?
  • Could this be a bug introduced in the latest version?

Any guidance or clarification would be greatly appreciated.

Hi @sumit.singhrawat1

Could you please share you is your HTTP Request activity configured right now?

(also, the latest WebAPI package is 2.3.0; there is no WebAPI 2.3.2 version)

Hi, apologies — I pasted the wrong info earlier. To clarify, I’m using UiPath.WebAPIActivity v2.3.0.

My concern is with the Postman API key integration in the Service Editor. Previously, I was able to load my Postman collection successfully using the API key, and it would appear under Services. But now, the same process results in an “Invalid Documents” error.

Here’s the process I followed:

  • Go to Postman → Profile → Settings → API Keys
  • Copy the API key
  • In UiPath Service Editor → Load via File or Link → Paste API key → Click Load

This used to work without issues, but now it fails to load the collection and throws the “Invalid Documents” error.

Could you please confirm:

  • Has anything changed in the way API keys are handled in the Service Editor?
  • Is this related to the WebAPIActivity update?
  • Is there a new recommended method for loading Postman collections?

Appreciate your guidance on this!

check this → Studio - API Test Automation

Hi, did you check my issue ? is there anything I need to update ?

Hi @sumit.singhrawat1

So, to summarize, the issue started occurring with the new version of UiPath Studio? (that import functionality is part of UiPath Studio, I believe)

I’m not sure what’s changed — I was previously able to add Postman collections using the service add option in UiPath by pasting the API key and loading the collection.
Now, this method isn’t working for me in UiPath Studio 2025.0.167 STS. I’m using an enterprise license,
and I’d like to know if this issue is affecting others too or if it’s just happening on my end. :slightly_smiling_face: