--- title: Chronosphere API Integration on Truto slug: chronosphere category: Incident Management canonical: "https://truto.one/integrations/detail/chronosphere/" --- # Chronosphere API Integration on Truto **Category:** Incident Management **Status:** Beta ## 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. - **Users** — The User object represents a User. ## MCP-ready AI tools Truto exposes 2 tools for Chronosphere that AI agents can call directly. - **list_all_chronosphere_teams** — List teams in Chronosphere. Returns each team's name, slug, description, user_emails, created_at, and updated_at in the response. - **get_single_chronosphere_team_by_id** — Get details about a specific team in Chronosphere using id. Returns name, slug, description, created_at, updated_at, and user_emails of the team. ## How it works 1. **Link your customer's Chronosphere 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 Chronosphere.** The Proxy API is a 1-to-1 mapping of the Chronosphere 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 Chronosphere Teams into Your Incident Routing Engine** — If you're building an incident management or on-call platform, you need to know which teams exist in your customer's Chronosphere workspace to route alerts correctly. Pulling team structures via Truto lets you map Chronosphere teams to your own escalation policies without manual configuration. - **Keep Dashboard Permissions in Sync with Your Identity Platform** — Identity governance and user directory SaaS products can read Chronosphere team membership to audit who has access to which observability dashboards. This enables automated compliance reporting and access reviews across your customers' toolchains. - **Enrich Your Platform's Org Chart with Observability Team Data** — HR tech and workforce analytics platforms can pull Chronosphere team structures to understand how engineering organizations are structured around services and infrastructure, enriching headcount planning and team topology insights. - **Auto-Map Service Ownership for Deployment Risk Analysis** — CI/CD and deployment platforms need to know which team owns a given service before triggering a rollout or rollback notification. Reading Chronosphere teams via Truto provides the ownership context needed to notify the right people automatically. ## What you can build - **Chronosphere Team Directory Sync** — Automatically import all Chronosphere teams and their member emails into your platform so users never have to manually recreate group structures. - **Team-Based Alert Routing Configuration** — Let your users select from their actual Chronosphere teams when setting up alert routing rules, populated in real time via the Truto Unified User Directory API. - **Ownership Lookup by Team ID** — Resolve a specific Chronosphere team by ID to display ownership details, member lists, and descriptions inline within your product's service catalog or incident timeline. - **Cross-Platform Group Reconciliation Dashboard** — Show your customers a side-by-side view of their Chronosphere teams versus groups in other connected tools, highlighting mismatches in membership or naming conventions. - **Automated Access Review Reports** — Generate periodic reports listing all Chronosphere team memberships for your customers' compliance teams, using Truto's unified groups and users model. ## FAQs ### What Chronosphere data can I access through Truto today? Truto currently supports reading Chronosphere team data via two tools: list_all_chronosphere_teams and get_single_chronosphere_team_by_id. These map to the Unified User Directory API (Groups). This gives you access to team names, slugs, descriptions, and member email arrays. ### Does Truto support write operations to Chronosphere? Currently, the available tools are read-only, covering team listing and lookup by ID. Write operations such as creating notifiers, muting rules, or events are not yet exposed through Truto's tool inventory. Contact Truto if you need write support for specific Chronosphere endpoints. ### How does authentication work for Chronosphere integrations via Truto? Chronosphere uses API tokens (service account tokens) for authentication. Your end users provide their Chronosphere API credentials when connecting their account through Truto, and Truto manages token storage and injection for all subsequent API calls. ### Does Truto handle pagination when listing Chronosphere teams? Yes. Truto abstracts away pagination details when using list_all_chronosphere_teams, so you receive a complete set of results without needing to manage page tokens or offsets yourself. ### Can I use the Unified User Directory API to normalize Chronosphere teams alongside groups from other tools? Exactly. Chronosphere teams are mapped to the Groups model in Truto's Unified User Directory API. This means you can query Chronosphere teams with the same schema and interface you use for groups from HRIS, identity providers, or other incident management tools — no tool-specific logic required. ### What data fields are available on a Chronosphere team object? A Chronosphere team object typically includes the team name, slug, description, and an array of user emails representing team members. These fields are mapped into Truto's unified Groups schema for consistent access across integrations.