We are announcing a new Xurrent integration now live within the Synqly ecosystem. Security and IT operations vendors building on Synqly can connect directly to Xurrent and give their OEM customers a path to create, update, and query tickets inside a customer’s Xurrent environment, without carrying the engineering cost of building and maintaining that connector on their own.
What is Xurrent?
Xurrent, formerly known as 4me, is a cloud-based IT and enterprise service management (ITSM/ESM) platform built around a shared service model that connects internal teams with external service providers on a single system of record. Where many ticketing platforms assume a single organization managing its own tickets end to end, Xurrent is designed for the more common enterprise reality: an internal IT team, a managed service provider, and one or more external vendors all need to see and act on the same request without losing track of who owns the next step.
What the Synqly Xurrent Integration Does
OEM customers building on Synqly can manage a customer’s Xurrent tickets through one consistent API, rather than learning Xurrent’s own ticketing model from scratch. Because Xurrent tickets are created and retrieved within the context of a specific project, the connector also exposes project and field discovery so a product can populate a new ticket correctly. Supported operations:
| Operation group | What it does |
| Create and retrieve tickets | Create a ticket, retrieve a ticket by ID, and patch a ticket to update its status or fields. |
| Query tickets | Filter by assignee, creator, priority, status, project, tags, and due date or completion date. |
| Comments and notes | Create a comment or a note, and list all comments or notes on a ticket to keep collaborators updated. |
| List projects | List the projects a customer has configured in Xurrent, the context every ticket is created and retrieved within. |
| List remote fields | Return the fields configured for each issue type across those projects, which a product needs before it can populate a new ticket. |
Together, these operations let a security or IT product open a ticket in a customer’s Xurrent instance automatically when it detects an issue, track that ticket through resolution, and keep collaborators updated through comments and notes, all through Synqly’s normalized Ticketing API.
Built on Synqly’s Standard Ticketing Interface
Because the integration is built on Synqly’s standard Ticketing interface, the same code a product team wrote to support Jira, ServiceNow, or another ticketing provider works with Xurrent without additional development. That matters most for vendors selling into managed service provider and enterprise service management environments where Xurrent is already the system of record. Full configuration and setup instructions live in the Xurrent Ticketing Configuration Guide on the Synqly documentation site.
Where to Find More Details
This is Xurrent’s first integration within the Synqly ecosystem. Full details, including supported operations and schema mappings, live on the Xurrent integration partner page. For hands-on setup, the Xurrent Ticketing Configuration Guide walks through generating a personal access token and locating the account and service instance identifiers Xurrent requires. A full list of every live integration is also maintained on the Synqly integrations page.
How the Ticketing Unified API Works
This Xurrent integration is part of Synqly’s Ticketing Unified API, which already connects OEM products to ticketing platforms including Atlassian Jira, ServiceNow, Zendesk, and PagerDuty, among others. The value of adding Xurrent is the same value the category delivers with every provider it supports.
A security or IT operations vendor whose customers already run on Xurrent should not have to choose between building a bespoke connector for that one account or asking the customer to adopt a different ticketing system just to work with the vendor’s product. Connecting through Synqly means a product team ships Xurrent support alongside every other ticketing platform Synqly supports, and picks up new platforms as Synqly adds them, without repeating that engineering effort for each customer who happens to run something different from the last.
Frequently Asked Questions
What is the Synqly Xurrent integration?
It is a connector that lets OEM security and IT operations products create, update, and query tickets in a customer’s Xurrent environment through Synqly’s Ticketing Unified API. Vendors get full ticket, comment, note, project, and field operations without building or maintaining a dedicated Xurrent API client.
What is Xurrent, and is it the same as 4me?
Yes. Xurrent is the current name for the platform formerly known as 4me. It is a cloud-based IT and enterprise service management platform built around a shared service model, connecting internal teams, managed service providers, and external vendors on a single system of record for a request.
What ticketing operations does the integration support?
Create a ticket, retrieve by ID, and patch to update status or fields; query tickets by assignee, creator, priority, status, project, tags, and due or completion date; create and list comments and notes; list projects; and list remote fields per issue type, which a product needs to populate a new ticket correctly.
Do engineering teams need to build a custom Xurrent connector?
No. The integration is built on Synqly’s standard Ticketing interface, so the same code a team wrote for Jira or ServiceNow works with Xurrent without additional development. Synqly handles authentication and normalization, and the product team configures the provider once instead of maintaining a bespoke Xurrent API client.
Who is the Xurrent integration for?
It is built for security and IT operations vendors whose customers use Xurrent as their system of record, especially those selling into managed service provider and enterprise service management environments. It lets those vendors support Xurrent customers without a one-off connector or asking the customer to switch ticketing systems.
Steven Erickson
https://www.synqly.comSteve brings a proven track record of turning complex technical challenges into scalable, user-centric products. Drawing on his experience leading engineering organizations at Styra, Illumio, and Juniper Networks, Steve shares his insights on product innovation, cloud-native security, and modernizing cybersecurity solutions. He is dedicated to building high-performing teams to fix the broken state of security integrations.
