--- title: Azure DevOps API Integration on Truto slug: azuredevops category: Ticketing canonical: "https://truto.one/integrations/detail/azuredevops/" --- # Azure DevOps API Integration on Truto **Category:** Ticketing **Status:** Generally available ## Unified APIs ### Unified CI/CD API - **Artifacts** — The artifact represent an artifact in the CI/CD. - **Branches** — The branch represent a branch in the CI/CD. - **Builds** — The build represent a build in the CI/CD. - **Jobs** — The job represent a job in the CI/CD. - **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. ### Unified Ticketing API - **Attachments** — Attachments are the files associated with a ticket or a comment. - **Comments** — Comments represent the communication happening on a Ticket, both between a User and a Contact and the internal things like notes, private comments, etc. A Ticket can have one or more Comments. - **Tags** — Tags represent a common classification approach used in various ticketing systems. A Ticket may have one or more Tags associated with them. - **Ticket Status** — Ticket Status represents the completion level of the Ticket. Some products provide customizing the Ticket Status. - **Ticket Types** — Ticket Types represent the classification system used by the underlying products for Tickets. Some examples are bugs, feature, incident, etc. - **Tickets** — Core resource which represents some work that needs to be carried out. Tickets are usually mapped to issues, tasks, work items, etc. depending on the underlying product. - **Users** — Users represent the people using the underlying ticketing system. They are usually called agents, team members, admins, etc. - **Workspaces** — Workspaces represent the top-level subdivision in a ticketing system. They usually have their own set of settings, tickets, statuses, priorities and users. Some of the usual terminologies used by the products for the top-level subdivision are projects, bases, spaces, workspace, etc. A Workspace could belong to an Organization. ### Unified Search API - **Search** — Search endpoint for all the apps. ## How it works 1. **Link your customer's Azure DevOps 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 Azure DevOps.** The Proxy API is a 1-to-1 mapping of the Azure DevOps 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 - **Escalate support tickets to engineering teams in Azure DevOps** — Customer support and CRM platforms can let agents push bug reports directly into Azure Boards as Work Items, then track resolution status back in real time — bridging the gap between frontline support and backend engineering without context-switching. - **Automate security vulnerability remediation workflows** — Application security and compliance SaaS products can automatically create high-priority Work Items in Azure DevOps when vulnerabilities are detected, routing them to the correct team via Area Paths and monitoring CI/CD pipelines to verify fixes are deployed. - **Aggregate engineering metrics across Azure Boards and Pipelines** — Engineering productivity platforms can ingest ticket lifecycle data alongside build and repo activity from Azure DevOps to calculate cycle time, deployment frequency, and sprint velocity — giving engineering leaders visibility without building bespoke ADO API integrations. - **Sync product roadmap items with Azure DevOps execution** — Product feedback and roadmapping tools can push strategic Features and Epics into Azure Boards and pull back real-time progress as child tasks are completed, keeping stakeholders aligned on delivery timelines. - **Centralize multi-tool ticketing data for enterprise customers** — Any SaaS product serving enterprise teams can offer Azure DevOps as a native integration alongside Jira and Linear, letting customers connect whichever ticketing tool they already use without your team building each integration from scratch. ## What you can build - **Two-way ticket sync with Azure Boards** — Keep Work Items (Bugs, Tasks, User Stories) synchronized between your product and Azure DevOps, including status changes, comments, and attachments flowing in both directions. - **Automated Work Item creation from external triggers** — Programmatically create Azure DevOps Work Items with the correct type, Area Path, and priority when your product detects an event — such as a security alert, customer escalation, or SLA breach. - **CI/CD pipeline visibility dashboard** — Surface Azure Pipelines build statuses, repo branches, and workflow runs directly inside your product so users can correlate code changes with ticket progress without leaving your UI. - **Cross-tool ticket search powered by WIQL** — Let users search and filter Azure DevOps Work Items using complex criteria — assignee, area path, state, iteration — through Truto's Unified Search API without your team learning WIQL syntax. - **Engineering cycle time analytics** — Combine ticket state transitions from Azure Boards with build and deployment data from Azure Pipelines to calculate end-to-end cycle time and DORA metrics for each team or project. - **Comment and attachment threading across platforms** — Sync rich-text comments and file attachments between your product and Azure DevOps Work Items so engineering and non-engineering stakeholders share a single conversation thread. ## FAQs ### What authentication methods does the Azure DevOps integration support? Azure DevOps supports OAuth 2.0 for Azure DevOps Services (cloud) and Personal Access Tokens (PATs). Truto handles the OAuth flow, token refresh, and credential storage so your team and your end users don't manage auth directly. ### Which Azure DevOps Work Item types can be mapped through the Unified Ticketing API? The Unified Ticketing API maps to Azure DevOps Work Items broadly — including Bugs, Tasks, User Stories, Epics, Features, and custom Work Item types. These are exposed through unified resources like Tickets, Ticket Types, and Ticket Status. ### How does Truto handle Azure DevOps pagination and rate limits? Azure DevOps enforces per-user and per-organization rate limits. Truto manages pagination automatically across list endpoints and handles rate-limit retries with backoff, so your integration doesn't need to implement this logic. ### Can I access custom fields on Azure DevOps Work Items? Yes. Azure DevOps supports extensive custom fields on Work Items. Truto can surface these through the integration, allowing you to read and write organization-specific fields that your end users have configured in their ADO projects. ### Does the integration support Azure DevOps webhooks for real-time updates? Azure DevOps provides Service Hooks for events like workitem.created, workitem.updated, and build.complete. Truto can leverage these to deliver real-time event notifications so your product reacts immediately to changes rather than relying solely on polling. ### What if I need an Azure DevOps capability that isn't covered by the current Unified APIs? Truto builds tools and custom proxy actions on request. If you need access to a specific Azure DevOps endpoint — such as Test Plans, Release Management, or advanced WIQL queries — the Truto team can extend coverage for your use case.