Query on building external API connector

Help Integration Service
1

I’m building an external API connector using the Integration Service. I was able to successfully create the connector and test an API call.

The challenge I’m facing is with the structure of the API itself. All API calls use a single base URL, and the specific operation or method is defined within the request body rather than in the URL path.

From what I can see, UiPath requires each API resource to have a unique API path. This doesn’t align with how my API is designed, as multiple operations share the same endpoint.

Because of this, I’m unable to duplicate the API call I successfully tested for another method. When I try, I receive the error: “Resource already exists.”

Looking for guidance on how to handle this type of API design within UiPath Integration Service.

2

image
image2824×1088 273 KB

3

Error:

image
image726×202 37.7 KB

4

Hi @ameya1

You can work around this by making each resource path unique using a dummy query parameter that your API ignores, like /portal/?id=1 and /portal/?id=2. Then hardcode the operation or method name in the request body for each resource. This lets you create separate, clearly named activities in Integration Service even though the backend uses the same endpoint.

1 Like
5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.