--- title: Rootly API Integration on Truto slug: rootly category: Incident Management canonical: "https://truto.one/integrations/detail/rootly/" --- # Rootly API Integration on Truto **Category:** Incident Management **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Groups** — Groups are a collection of users in the source application. In some applications, they might also be called Teams. - **Me** — - **Users** — The User object represents a User. ## How it works 1. **Link your customer's Rootly account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Rootly.** The Proxy API is a 1-to-1 mapping of the Rootly API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Sync responder directories for accurate on-call routing** — Identity, HR, or workforce management platforms can use Truto's Unified User Directory API to map their user and group models to Rootly's users and teams, ensuring on-call schedules always reflect current org structure and offboarded employees are never paged. - **Automate incident creation from security or observability findings** — Cloud security, APM, or observability SaaS products can trigger Rootly incidents programmatically when critical issues are detected, giving their customers instant Slack-based war rooms without leaving the detection tool. - **Bi-directionally sync post-incident action items with task trackers** — Project management and engineering workflow platforms can pull Rootly action items into their own systems and push status updates back, making post-incident follow-through seamless for SRE and engineering teams. - **Deflect support tickets during active incidents** — Helpdesk and customer support SaaS products can query Rootly for active incidents tied to specific services, automatically linking incoming tickets to known outages and reducing noise for both support agents and engineering responders. - **Keep service catalogs in sync across platforms** — Internal developer portals and CMDB tools can push service and environment metadata into Rootly's catalogs, ensuring incident responders always have accurate infrastructure context when triaging. ## What you can build - **Automated user and team provisioning in Rootly** — Use Truto's Unified User Directory API to sync users, groups, and team memberships from your platform into Rootly so on-call rosters stay current as people join, leave, or change roles. - **One-click incident declaration from external alerts** — Let your users trigger fully-configured Rootly incidents—with severity, affected service, and environment—directly from your product's alert or finding detail page. - **Real-time offboarding enforcement for on-call schedules** — Automatically deactivate or reassign Rootly on-call responsibilities when a user is deprovisioned in your identity or HR platform, preventing critical pages from going to ghost accounts. - **Post-incident action item sync dashboard** — Surface Rootly retrospective action items as native tasks in your project management tool with status synced in both directions so nothing falls through the cracks. - **Incident-aware support ticket routing** — Automatically tag and group incoming support tickets that match an active Rootly incident, presenting agents with live incident status and reducing duplicate escalations. - **Org-chart-driven responder group management** — Map your platform's organizational groups to Rootly teams using the Unified User Directory API, so department or squad changes instantly propagate to incident response structures. ## FAQs ### Which Truto Unified APIs are available for Rootly today? Rootly is supported through Truto's Unified User Directory API, which covers Users, Groups, and Me resources. This lets you read and manage user and team data in Rootly through a standardized schema. ### Are incident, action item, or catalog-specific tools available through Truto? Not yet as pre-built unified tools, but Truto can build custom tools for Rootly's incident, action item, catalog, and retrospective endpoints on request. Rootly's API follows the JSON:API specification, and Truto handles auth, pagination, and schema mapping for you. ### What authentication method does Rootly use? Rootly uses API token-based authentication. Your end users generate an API token from their Rootly account, and Truto securely stores and manages the credential so you never handle raw tokens in your own infrastructure. ### How does Truto handle Rootly's JSON:API pagination? Truto abstracts away Rootly's cursor-based JSON:API pagination. You make a single request through Truto's unified interface and receive normalized, fully-paginated results without writing custom pagination logic. ### Can I map Rootly teams to groups in the Unified User Directory API? Yes. Rootly's native Teams concept maps to the Groups resource in Truto's Unified User Directory API, allowing you to list, create, and manage team memberships through a consistent schema shared across all directory integrations. ### How quickly can I get a custom Rootly integration built if I need endpoints beyond User Directory? Truto builds custom integrations on request. Once you specify the Rootly endpoints and data models you need—such as Incidents, Action Items, or Catalogs—the Truto team delivers a fully managed integration with normalized schemas, auth handling, and error management.