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 Pipelines Artifacts API

Operations for listing and retrieving artifacts produced by pipeline runs including compiled outputs, test results, and published files.

Azure Pipelines Artifacts API is one of 11 APIs that Azure Pipelines publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 1 operation across 1 path, and defines 2 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.

1 operations 1 paths 2 schemas 1 GET

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
Authentication
HTTP Bearer, HTTP Basic
Terms of Service
Resource Areas
1

Authentication & Security 2

Azure Pipelines Artifacts API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • bearerAuth — Azure AD OAuth 2.0 bearer token with vso.build scope
  • basicAuth — Basic authentication using a Personal Access Token (PAT)

Paths & Operations 1

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

Artifacts 1

Operations for listing and retrieving artifacts produced by pipeline runs including compiled outputs, test results, and published files.

GET
/pipelines/{pipelineId}/runs/{runId}/artifacts
Azure Pipelines List run artifacts
listRunArtifacts 5 params → 200401403404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are ApiError (6 properties), PipelineArtifact (3 properties). Each schema is shown below with its type and property counts.

PipelineArtifact
object
An artifact produced by a pipeline run
3 properties
ApiError
object
Error response from the Azure DevOps API
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microsoft-azure-pipelines-artifacts-api-openapi.yml Raw ↑

Other APIs Azure Pipelines publishes across the network.

Azure Pipelines Build REST API
Azure Pipelines Release REST API
Azure Pipelines Approvals and Checks REST API
Azure Pipelines Build Artifacts API
Azure Pipelines Build Definitions API
Azure Pipelines Build Tags API
Azure Pipelines Builds API
Azure Pipelines Logs API
Azure Pipelines Pipelines API
Azure Pipelines Runs API
Where this information came from

This is an independent, third-party profile of Azure Pipelines Artifacts 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.