How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Automate Builds, Pull Requests And Releases With Azure DevOps

November 18th, 2026 · Kin Lane
Automate Builds, Pull Requests And Releases With Azure DevOps

If your team builds software, a lot of the week disappears into small, repeated chores. Kicking off a build, checking whether it passed, opening a pull request, filing a bug, pushing a release out to the next environment, and then telling everyone it happened. Most teams do these by clicking through screens. Azure DevOps lets you do all of them through an API, which means a script, an internal tool, or an AI assistant can do the clicking for you.

An API is a set of doors into a service that other software can knock on. Instead of a person logging in, a program sends a request and gets an answer back. That is what turns a tool your developers use into something the rest of the business can automate around.

What Azure DevOps does

Azure DevOps is Microsoft’s set of developer services for teams to plan work, collaborate on code, and build and deploy applications. It covers the backlog (Azure Boards), the code (Azure Repos), the builds and releases (Azure Pipelines) and the testing (Test Plans). You can find it through Microsoft.

What you can get done

Run and track your builds

Continuous Integration Management is the practice of building and checking your software automatically every time someone changes it. The API lets you define the build, start it, and find out whether it worked, so a status page or a chat bot can answer “is main green?” without anyone opening a dashboard.

  • GET /build/definitions lists the build pipelines set up in a project.
  • POST /build/definitions creates a new build pipeline.
  • POST /build/builds queues a build of a chosen pipeline on a chosen branch.
  • GET /build/builds lists recent builds, filtered by status, result or who asked for them.
  • GET /build/builds/{buildId} tells you whether a build succeeded and what code it ran against.

Manage code reviews

Software Construction Management covers the day-to-day handling of code: repositories, commits and pull requests. A pull request is a proposed change that teammates review before it is merged in. Automating it means you can open, comment on and close reviews from your own tools.

  • GET /git/repositories/{repositoryId}/pullrequests lists the open pull requests in a repository.
  • POST /git/repositories/{repositoryId}/pullrequests opens a new pull request.
  • PATCH /git/repositories/{repositoryId}/pullrequests/{pullRequestId} completes, abandons or retargets one.
  • POST /git/repositories/{repositoryId}/pullrequests/{pullRequestId}/threads leaves a review comment.
  • GET /git/repositories/{repositoryId}/commits lists commits, for example between two dates.

Ship releases to each environment

Software Release & Deployment Management is about moving a finished build into testing, staging and production in a controlled way.

  • GET /release/definitions lists the release pipelines in your project.
  • POST /release/releases starts a new release, optionally as a draft.
  • GET /release/releases/{releaseId} shows the deployment status of each environment.
  • GET /release/deployments lists deployments, so you can see which failed last week.

Keep the backlog moving

Product Discovery & Backlog Management covers the work items your team plans and tracks: bugs, tasks and stories.

  • POST /wit/workitems/{type} files a new bug or task.
  • GET /wit/workitems/{id} returns the current state of a work item.
  • PATCH /wit/workitems/{id} changes its state or assignee, or links it to another item.

Tell other systems when things happen

With Webhook & Event Subscription Management you can have Azure DevOps call your own endpoint when something happens, like a code push. POST /hooks/subscriptions sets that up and GET /hooks/subscriptions lists what is already in place. Testing has its own capability too, Software Quality Engineering, where POST /testplan/plans creates a test plan for a sprint.

Workflows that put it together

A workflow is a recipe: several API calls made in a set order to finish one job. These are written in Arazzo, an open format for describing those recipes so software can follow them.

Ask for it in plain language

We publish a conversational overlay for these APIs, which maps everyday questions to the operation that answers them, so an AI assistant knows which call to make. These are the kinds of questions it covers:

  • “Which builds failed on the main branch recently?”
  • “How do I kick off a build of a specific definition on a chosen branch?”
  • “Which pull requests are still open against main in a repository?”
  • “How do I file a new bug in Azure Boards?”
  • “What is the deployment status of each environment in a release?”
  • “How do I send a webhook to my endpoint whenever code is pushed?”

You can see one of them in the Build Definitions phrasing overlay.

Getting started

Azure DevOps is paid with a free trial and self-serve signup. One example from the Pricing section of the profile is $40 per extra Microsoft-hosted CI/CD parallel job. Microsoft’s documentation covers the Core API, the Graph API and authentication.

On APIs.io you can browse the full Azure DevOps profile and individual APIs such as the Core API, the Search API, the Audit API and the Policy API.

Pick the one chore your team repeats most, probably “did the build pass?”, and automate that first.