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 DevOps Feeds API

Operations for managing artifact feeds

Azure DevOps Feeds API is one of 62 APIs that Azure DevOps publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Feeds. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, an API reference, and an AsyncAPI specification.

This API exposes 5 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 7.1.

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

5 operations 2 paths 6 schemas 1 DELETE2 GET1 PATCH1 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}
Authentication
HTTP Bearer, HTTP Basic
License
Resource Areas
1

Authentication & Security 2

Azure DevOps Feeds 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
  • basicAuth — Basic authentication using a Personal Access Token (PAT). Use any string as the username and the PAT as the password, then base64-encode the result.

Paths & Operations 5

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

Feeds 5

Operations for managing artifact feeds

GET
/packaging/feeds
Azure DevOps List feeds
feeds_list 4 params → 200401403
POST
/packaging/feeds
Azure DevOps Create a feed
feeds_create 1 param body → 200400401403
GET
/packaging/feeds/{feedId}
Azure DevOps Get a feed
feeds_get 3 params → 200401403404
PATCH
/packaging/feeds/{feedId}
Azure DevOps Update a feed
feeds_update 2 params body → 200400401403404
DELETE
/packaging/feeds/{feedId}
Azure DevOps Delete a feed
feeds_delete 2 params → 204401403404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Feed (13 properties), UpstreamSource (7 properties), FeedUpdateRequest (6 properties), FeedCreateRequest (6 properties). Each schema is shown below with its type and property counts.

Feed
object
An Azure Artifacts package feed
13 properties
ApiError
object
Error response from the Azure DevOps API
6 properties
FeedView
object
A view of a feed (e.g., @local, @prerelease, @release)
5 properties
UpstreamSource
object
An upstream package source configured for a feed
7 properties
FeedCreateRequest
object
Parameters for creating a new feed
6 properties 1 required
FeedUpdateRequest
object
Parameters for updating a feed
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microsoft-azure-devops-feeds-api-openapi.yml Raw ↑

Other APIs Azure DevOps publishes across the network.

Azure DevOps Graph API
Azure DevOps Core API
Azure DevOps Security API
Azure DevOps Notifications API
Azure DevOps Audit API
Azure DevOps Search API
Azure DevOps Policy API
Azure DevOps Distributed Task API
Azure DevOps Analytics OData API
Azure DevOps Extension Management API
Azure DevOps Service Endpoint API
Azure DevOps TFVC API
Where this information came from

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