Insights & updates from our experts
A new security feature has been added to Xurrent’s Webhooks API. This feature ensures that Xurrent verifies whether a webhook’s endpoint is actually owned by the organization that specified the endpoint in the webhook.
Now, when a new webhook is registered, Xurrent immediately sends a webhook.verify message to the endpoint specified in the URI field of the webhook. The payload of this webhook message contains a callback parameter that must be called to prove ownership of the endpoint. A webhook is inactive until the verification callback is received by Xurrent.

Xurrent considers all webhooks that already existed ‘verified’ so the extra verification step is required only for new webhooks and webhooks in which the value in the URI field is updated.
More information about Webhook verification can be found in the Xurrent Developer Documentation.

An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.















.webp)
.webp)


.webp)











