--- title: Buddy API Integration on Truto slug: buddy category: CI/CD canonical: "https://truto.one/integrations/detail/buddy/" --- # Buddy API Integration on Truto **Category:** CI/CD **Status:** Generally available ## Unified APIs ### Unified CI/CD API - **Branches** — The branch represent a branch in the CI/CD. - **Jobs** — The job represent a job in the CI/CD. - **Pull-Requests** — - **Repos** — The repo represent a repository in the CI/CD. - **Workflow** — The workflow represent a CI/CD workflow. - **Workspaces** — The Workspace object is used to represent a workspace within a company. ## How it works 1. **Link your customer's Buddy 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 Buddy.** The Proxy API is a 1-to-1 mapping of the Buddy 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 - **Aggregate CI/CD health across tools in a developer portal** — Internal developer platform (IDP) companies can pull Buddy's pipeline executions, branches, and repos into a unified deployment health dashboard alongside other CI/CD tools, giving engineering teams a single pane of glass without building provider-specific adapters. - **Trigger automated security scans on successful builds** — DevSecOps SaaS products can monitor Buddy workflow executions and automatically kick off vulnerability scans when a staging deployment succeeds, blocking production pipelines if critical issues are found — all without requiring users to configure webhooks manually. - **Auto-provision CI/CD pipelines from a hosting platform** — Vertical hosting or PaaS products can let their customers connect a Buddy account, then programmatically create workspaces, configure deployment workflows, and wire up continuous delivery — so users never leave the hosting dashboard. - **Sync build statuses into project management tools** — Agile and project management SaaS companies can read Buddy job statuses and map them to issue lifecycle stages, automatically transitioning tickets when builds pass or fail without teams switching context. - **Power AI-driven build failure analysis** — AI code-review and developer productivity tools can fetch Buddy execution logs and job metadata to surface root-cause analysis on failed builds, providing actionable fix suggestions directly in the developer's workflow. ## What you can build - **Unified deployment history timeline** — Display a chronological view of Buddy pipeline executions alongside other CI/CD providers, showing commit hashes, statuses, and durations in one normalized feed. - **One-click rollback from your dashboard** — Let users trigger a Buddy pipeline execution targeting a previous known-good revision directly from your product's UI using the Unified CI/CD API's workflow and job models. - **Automated pipeline scaffolding on customer onboarding** — Programmatically create Buddy workspaces and workflows when a new customer signs up, pre-configured with your platform's deployment keys and environment settings. - **Branch-aware deployment status badges** — Pull branch and job data from Buddy to render real-time build status indicators per feature branch inside your product's repo or PR views. - **Cross-tool CI/CD analytics dashboard** — Aggregate jobs, workflows, and repo metadata from Buddy and other providers to compute metrics like mean time to deploy, failure rate, and build queue duration. - **Deployment-gated feature flags** — Monitor Buddy job completions and automatically enable or disable feature flags in your product based on whether the latest production deployment succeeded or failed. ## FAQs ### What Unified API resources does Truto map to Buddy? Truto's Unified CI/CD API covers Branches, Jobs, Pull-Requests, Repos, Workflows, and Workspaces. Buddy's projects map to Repos, pipelines to Workflows, executions to Jobs, and workspaces to Workspaces. Specific tools for Buddy are built on request — contact Truto to enable them. ### How does authentication work for Buddy through Truto? Buddy supports OAuth 2.0 and personal access tokens for API access. Truto handles the OAuth flow and token refresh for your end users, so you don't need to manage credentials or re-authentication yourself. ### Can I both read and write data to Buddy through the integration? Yes. Buddy's API supports read operations (listing projects, pipelines, executions) as well as write operations (creating pipelines, triggering executions, managing environment variables). Truto can expose both read and write capabilities once the Buddy connector is built for your account. ### Are there rate limits I should be aware of with Buddy's API? Buddy applies rate limits on its API. Truto manages pagination and request throttling on your behalf, so your integration handles large workspaces with many pipelines and executions without hitting limits or writing retry logic. ### How fresh is the data when reading Buddy pipelines and executions? Data is fetched in real time from Buddy's API on each request through Truto. There is no intermediate caching layer that would introduce staleness — you get the current state of workspaces, workflows, and jobs as Buddy reports them. ### What if Buddy doesn't have a direct concept for Pull Requests? Buddy pipelines are typically triggered by events from connected Git providers (GitHub, GitLab, Bitbucket), which own the pull request data. Truto's Unified CI/CD API normalizes PR-related metadata where available, but the depth of PR data depends on the Git provider linked to the Buddy project.