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

Azure Repos Refs API

Operations for managing branches and tags (refs) including listing, creating, updating, and deleting refs.

Azure Repos Refs API is one of 9 APIs that Azure Repos publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Refs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, rate-limit docs, an API reference, and a getting-started guide.

This API exposes 2 operations across 1 path, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 7.1.

Requests are made against a single base URL, https://dev.azure.com/{organization}/{project}/_apis.

2 operations 1 paths 4 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
7.1
Base URL
https://dev.azure.com/{organization}/{project}/_apis/git
Authentication
OAuth 2.0, HTTP Basic
License
Terms of Service
Resource Areas
1

Authentication & Security 2

Azure Repos Refs API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 3 scopes. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • oauth2 — OAuth 2.0 authorization code flow for Azure DevOps Services. Requires the vso.code scope for read operations and vso.codewrite for write operations.
  • basicAuth — HTTP Basic authentication using a Personal Access Token (PAT). Use any string for the username and the PAT as the password.

Paths & Operations 2

Across 1 path, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Refs 2

Operations for managing branches and tags (refs) including listing, creating, updating, and deleting refs.

GET
/git/repositories/{repositoryId}/refs
Azure Repos List refs (branches and tags)
refs_list 8 params → 200401404
POST
/git/repositories/{repositoryId}/refs
Azure Repos Create, update, or delete refs
refs_update 1 param body → 200401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are GitRef (8 properties), GitStatus (8 properties), IdentityRef (7 properties), GitRefUpdateResult (6 properties). Each schema is shown below with its type and property counts.

GitStatus
object
Status metadata posted by a service or extension against a commit or pull request, such as build results or policy checks.
8 properties
GitRef
object
A Git ref (branch or tag) including its name, object ID, and optional creator and status information.
8 properties
GitRefUpdateResult
object
Result of a ref update operation
6 properties
IdentityRef
object
Reference to an Azure DevOps identity (user or group)
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microsoft-azure-repo-refs-api-openapi.yml Raw ↑

Other APIs Azure Repos publishes across the network.

Azure Repos Commits API
Azure Repos Items API
Azure Repos Pull Request Reviewers API
Azure Repos Pull Request Threads API
Azure Repos Pull Requests API
Azure Repos Pushes API
Azure Repos Repositories API
Azure Repos Stats API
Where this information came from

This is an independent, third-party profile of Azure Repos Refs API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.