Webhook trigger endpoint returns 401

[Feier]

@mohitjain

Hi @bamieh,

Thank you for the detailed report. This is a confirmed regression of the same server-side issue that affected webhook triggers in late March. The error is not related to your API key or anything on your end.

Our engineering team is aware that this has recurred and is actively working on a permanent fix for the underlying cause. There is no workaround at this time since the issue is entirely server-side.

I’ve also noted the reports from @ItayA and @redefinered-cc — this is the same issue.

I’ll update here once the fix is deployed. Apologies again for the disruption

Same issue here. I trigger automations programmatically from a self-hosted agent running on a VPS. Started getting the same ERROR_NOT_LOGGED_IN / 500 responses on April 3-4.

Confirmed:

• API key authenticates fine (GET /v0/agents returns 200)

• POST to both api2.cursor.sh/automations/webhook/ and api.cursor.com/v0/agents return 500

• Manual trigger from the dashboard UI still works

• Regenerating API keys doesn’t help

• Plan upgrade doesn’t help

Appreciate the quick acknowledgement. Following for the fix.