Webhook suddenly disabled and API calls returning unauthorized

Help Orchestrator
,
1

Hi UiPath Team & Community,

I’m reaching out on behalf of our nonprofit organization, Cyber Awareness Welfare Society

WhatsApp Image 2025-07-01 at 14.47.03
WhatsApp Image 2025-07-01 at 14.47.03962×623 95.7 KB

. Over the past 2 months, we’ve worked incredibly hard to understand and integrate UiPath into our automation workflows — with the intent to help underserved communities through technology.

Everything was going well until this morning, when we noticed:

  • The webhook feature was suddenly disabled
  • API calls from Postman that previously worked began returning 401 Unauthorized
  • We regenerated tokens and rechecked headers — nothing worked

We’ve tried to contact the support team through the official Contact Us page multiple times but received no reply yet.

Here’s what we’ve verified so far:

  • The Authorization: Bearer token is freshly generated via API Access
  • The X-UIPATH-OrganizationUnitId header is correct
  • The endpoints (e.g. /odata/Jobs, /odata/Assets) were working until early this morning
  • UiPath Assistant also started giving occasional popups: “An object could not be cloned”

We don’t know if this is an account-level restriction, or if webhook/API access is being deprecated at the community tier.

We would be grateful for clarification or escalation. This automation project is central to our mission — and without API access, we are stuck.

Sincerely,
Deepak
Cyber Awareness Welfare Society

2

Hello Deepak,

Welcome to the community, cool to hear your NGO is getting use of UiPath.

The answer you seek is on that blue banner in your screenshot, it explains that the triggers there will no longer be available from June 30th and must instead be made in the Orchestrator.

3

WhatsApp Image 2025-07-01 at 14.47.03
WhatsApp Image 2025-07-01 at 14.47.03962×623 95.7 KB

Has the API trigger also been turned off? Because we had taken the API trigger from Postment last night. Which was working fine. Now it is showing the same hit as unathorised

4

I am not sure what you mean by it being unauthorised, but the existing triggers should be still available in this section, but its instructed that you need to remake them in the Orchestrator, so I’d suggest doing that.