Specialist Coded Agent Challenge: Build with UiPath SDK & LangChain/LLamaIndex and win up to $10,000

News Events
14

Am exploring the SDK, as the competition gives nice and clear objectives as guidelines. Not interested in participating, because I will never sign away all rights (including to my appearance in a required video with facecam!?! UiPath, I have some very choice words for that.), which would prevent me from using the code without WRITTEN UiPath PERMISSION at work. And too lazy to find usecases guaranteed outside my job.
(And not even bothering my employer’s legal team with such a competition, would be waste of time. Inacceptable legal terms.)

That does free me up to share some tips & tricks to other entrants: I just listed all context grounding* files straight within the Python SDK implementation. Here is how:

*) core requirement for submissions

Read the Fine Source: UiPath Python SDK has an undocumented escape hatch for raw API calls :slight_smile:

When the UiPath Python SDK doesn’t expose the endpoint you need, use sdk.api_client for direct HTTP requests:

from uipath import UiPath

sdk = UiPath()

High-level SDK (limited endpoints)

index_name = "MyIndex"
index = sdk.context_grounding.retrieve(
    name=index_name,
    folder_key=folder_key  # SDK uses folder_key (GUID)
)

Low-level API client (any endpoint)

files_response = sdk.api_client.request(
    "GET",
    f"/orchestrator_/odata/Buckets({bucket_id})/UiPath.Server.Configuration.OData.GetFiles",
    params={"directory": "/", "recursive": "true"},
    headers={"X-UIPATH-OrganizationUnitId": str(folder_id)}  # Reuse again!
)

files = files_response.json()["value"]

Key Features

  • Automatic authentication - reuses SDK’s OAuth token
  • Built-in retries - inherits SDK retry logic
  • Folder context - use include_folder_headers=True to auto-inject folder headers
  • Async support - await sdk.api_client.request_async(…)

Use Cases

  • Listing files in storage buckets (no SDK method exists)
  • Accessing OData endpoints not wrapped by SDK
  • Calling newer API endpoints before SDK updates
  • Debugging/troubleshooting with direct API access

Source

Officially documented:
uipath-python/src/uipath/_services/api_client.py at main · UiPath/uipath-python · GitHub
(for values of “official” equal to “in the source” :wink: )

“Low-level client for making direct HTTP requests to the UiPath API when the higher-level service classes don’t provide the needed functionality.”

Reference Swagger specs at https://cloud.uipath.com/{account}/{tenant}/orchestrator_/swagger/ for available endpoints (a.k.a. the Orchestrator API specs).

Request for Comments

I quite like the convenience that a extention package gives me. For those to take this challenge, maybe we can compare pain points? Even after the deadline?

Here is a RfC with what I have in mind: Proposed uipath-sdk-extensions RFC — demonstrates authentication and folder context reuse for UiPath Cloud. Includes full working examples showing .env setup, SDK initialization, context caching, and direct API integration using sdk.api_client. · GitHub

The whl is publicly available, but I am only motivated to take the library code out of my monorepo if there are >10 stars on the gist and at least 3 constrcutive comments.

All of those with the skills to take part in this challenge will certainly understand the value of shared code.

9 Likes