Unparseable webhook endpoint URLs return 422 instead of 500

POST /api/v2/workspaces/{workspace_id}/webhooks/outgoing/endpoints and PUT /api/v2/webhooks/outgoing/endpoints/{id} used to answer 500 when url was something a URI parser refuses, such as a path with a literal space, a non-ASCII hostname or a bare mailto:. They now return 422 carrying the same "URL not valid" message the Webhooks settings page shows, and nothing is saved.

A 500 looked like an outage on our side and gave a retry loop nothing to act on. A 422 names the field, so your integration can hand the bad URL back to whoever typed it instead of retrying a request that will never succeed.

Agent examples: fail an endpoint setup step with the exact URL problem instead of a generic server error · stop retrying a webhook registration that is being rejected for its URL.

Resources: Endpoint