The error message:

"webhook response could not be unmarshalled properly from JSON: invalid character 'T' looking for beginning of value"

indicates that Ory is expecting a JSON response from your webhook, but it received something else—likely a plain text response or a response starting with a character like 'T' (for example, "This is not JSON..."). This typically happens when: - The webhook endpoint returns a non-JSON response (such as plain text or HTML) when Ory expects JSON. - There is a misconfiguration in the webhook, such as an incorrect URL, authentication failure, or the endpoint is returning an error page instead of the expected JSON payload. - The webhook server in production is behaving differently than in other environments (e.g., different error handling, different content-type headers, or a proxy/load balancer modifying responses). A similar issue was reported where editing a webhook in the Ory Console caused authentication credentials (like a password) to be lost, resulting in the webhook failing and returning an unexpected response. Re-entering the correct credentials resolved the issue. This suggests that webhook authentication or configuration differences between environments could be the culprit in your case as well. The Ory team recommends double-checking your webhook configuration, especially after making edits, and ensuring the endpoint always returns valid JSON when Ory expects it. You may also want to use the Ory CLI to update webhooks as a workaround if the Console is causing issues with credentials[editing action/webhook changes basic auth password](https://github.com/ory/network/issues/416). Action steps: - Ensure your webhook endpoint always returns a valid JSON response with the correct content-type. - Check for differences in webhook configuration between production and other environments, especially authentication. - If you recently edited the webhook in the Ory Console, try re-entering the authentication credentials. If the issue persists, reviewing the actual response body from your webhook in production (using logs or a tool like Postman) can help pinpoint what is being returned and why it fails to parse as JSON.

The knowledge sources do not explicitly mention a built-in feature in Ory Network or Ory Console that allows you to directly monitor which specific webhook endpoint caused a problem, such as a failed response or parsing error, in the main Ory Actions or Identities webhooks system. However, for Ory Polis Directory Sync webhooks, if webhook event logging is enabled, you can view webhook events (including failures) in the Admin Portal under the Webhook Events tab for each directory sync connection. This allows you to see the raw event data and may help you identify which endpoint had issues. By default, webhook events are not logged, but you can enable this feature in the Admin Portal settings for your directory sync connection[Manage directories](https://www.ory.sh/docs/polis/admin-portal/directory-sync). For Ory Actions and Identities webhooks, the documentation suggests troubleshooting by checking configuration and logs, but does not describe a UI or log view that directly shows which webhook endpoint failed or caused a parsing error. You may need to rely on your own webhook server logs or error messages returned by Ory (which may include the request ID) to trace the problematic endpoint[Troubleshoot Ory Actions Webhook issues](https://www.ory.sh/docs/troubleshooting/troubleshoot-actions). If you need more detailed monitoring, consider implementing logging on your webhook endpoints to capture incoming requests and errors for further analysis.