--- title: BigPanda API Integration on Truto slug: bigpanda category: Incident Management canonical: "https://truto.one/integrations/detail/bigpanda/" --- # BigPanda API Integration on Truto **Category:** Incident Management **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Roles** — The Role object represents a role of a User. - **Users** — The User object represents a User. ## How it works 1. **Link your customer's BigPanda 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 BigPanda.** The Proxy API is a 1-to-1 mapping of the BigPanda 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 - **Push monitoring alerts into BigPanda for AI-powered correlation** — If you're building an observability or infrastructure monitoring SaaS, your enterprise users already rely on BigPanda to correlate and deduplicate alerts. Offering a native BigPanda integration lets them route your alerts directly into their incident management workflow without manual configuration. - **Sync incident lifecycle between your service desk and BigPanda** — ITSM and ticketing platforms can offer two-way incident sync with BigPanda — automatically creating tickets when BigPanda surfaces a correlated incident, and resolving the BigPanda incident when an engineer closes the ticket. This eliminates context-switching and keeps both systems in lockstep. - **Trigger automated remediation from BigPanda incidents** — Runbook automation and self-healing platforms can listen for BigPanda incidents, retrieve AI-generated root cause analysis, and execute targeted remediation scripts — then post results back to BigPanda as comments for full audit trail visibility. - **Enrich BigPanda incidents with deployment and change context** — CI/CD and release management tools can push change records into BigPanda so that NOC teams instantly see whether an incident correlates with a recent deployment. This dramatically shortens mean time to resolution for your shared enterprise customers. - **Sync user roles and permissions across your platform and BigPanda** — Enterprise customers managing large NOC teams need consistent user provisioning across tools. Using Truto's Unified User Directory API, you can read BigPanda user and role data to keep access controls aligned with your own platform's identity model. ## What you can build - **One-click alert forwarding to BigPanda** — Let your users configure a BigPanda destination that automatically POSTs normalized alerts — including status, severity, and custom tags — into BigPanda's Open Integration Manager whenever a threshold is breached. - **Bi-directional incident status sync** — Build a feature that subscribes to BigPanda incident webhooks to create tickets in your platform, and pushes resolution or comment updates back to BigPanda's Incidents API when your users take action. - **AI root cause summary display** — Surface BigPanda's Automated Incident Analysis — plain-language root cause estimations and impact summaries — directly inside your product's incident detail view so users never have to switch tabs. - **Change-incident correlation overlay** — Push deployment and change records from your CI/CD pipeline into BigPanda's Changes API so your users can visually correlate production incidents with recent releases on a shared timeline. - **Unified user and role directory sync** — Leverage Truto's Unified User Directory API to read BigPanda users and roles, enabling automated provisioning dashboards or access audits within your own platform. - **Incident search and reporting dashboard** — Query BigPanda incidents using BPQL filters — by environment, source system, or time range — and render aggregated incident metrics, alert counts, and MTTR trends inside your product's analytics module. ## FAQs ### What authentication method does BigPanda use for API access? BigPanda uses bearer token authentication. API consumers pass an API key (generated in the BigPanda admin console) in the Authorization header. Truto handles token storage and injection so your end users only need to provide their credentials once during the connection flow. ### Are BigPanda tools available out of the box in Truto? BigPanda integration tools are built on request. Once you indicate interest, the Truto team will scope and build the specific API resources you need — such as Alerts, Incidents, Changes, or Webhooks — tailored to your use case. The Unified User Directory API (Users and Roles) is already mapped. ### What data can I access through Truto's Unified User Directory API for BigPanda? You can read BigPanda user records and their associated roles. This is useful for provisioning workflows, access audits, and keeping identity data consistent between your platform and your customers' BigPanda accounts. ### Does BigPanda support real-time event delivery or do I need to poll? BigPanda supports outbound webhooks via its Notifications API. You can subscribe to real-time incident lifecycle events — creation, updates, state changes — which eliminates the need for polling in most outbound sync scenarios. ### Can I query BigPanda incidents with filters? Yes. BigPanda's Incidents V2 API supports BPQL (BigPanda Query Language), which lets you filter incidents by environment, tags, source system, time frame, and more. You can also expand the payload to include underlying alert-level detail. ### How does Truto handle pagination and rate limits for BigPanda? Truto abstracts away pagination and rate-limit management. When BigPanda enforces API rate limits or returns paginated results, Truto automatically handles retries, back-off, and cursor-based iteration so your application receives a clean, complete dataset.