Azure DevOps (via Apideck Proxy)

Access Azure DevOps through Apideck's Proxy API with managed Vault auth. Apideck stores credentials, refreshes tokens, and forwards your HTTP calls to Azure DevOps's native API — you keep using Azure DevOps's own request and response shapes, while Apideck eliminates per-tenant credential plumbing and gives you a single auth integration shared across every Apideck connector.

Auth-only / proxy-only connector. Apideck does not map Azure DevOps to a unified-API resource model — your code talks Azure DevOps's own API directly through the Proxy. You still get Vault credential storage, token refresh, retries, and a consistent request envelope.

Quick facts

• Apideck serviceId: azure-devops
• Mode: Proxy-only (no unified API resources)
• Auth type: basic
• Status: beta
• Gotchas: page
• Azure DevOps docs: https://learn.microsoft.com/en-us/rest/api/azure/devops/
• Homepage: https://azure.microsoft.com/en-us/products/devops

When to use this skill

Activate this skill when the user wants to call Azure DevOps via Apideck — for example, "call the Azure DevOps API" or "fetch data from Azure DevOps". This skill teaches the agent: