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.

A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

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)














