メニュー
Azure DevOps via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Azure DevOps's native API. Use when the user wants to call Azure DevOps (no unified API resource mapping). Routes through Apideck with serviceId "azure-devops".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | azure-devops |
| description | Azure DevOps via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Azure DevOps's native API. Use when the user wants to call Azure DevOps (no unified API resource mapping). Routes through Apideck with serviceId "azure-devops". |
| license | Apache-2.0 |
| alwaysApply | false |
| metadata | {"author":"apideck","version":"1.0.0","serviceId":"azure-devops","proxyOnly":true,"unifiedApis":[],"authType":"basic","tier":"2","verified":true,"status":"beta"} |
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.
azure-devopsActivate 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:
serviceId to pass on every call (azure-devops)If you need a unified-API surface (one method shape across many vendors), see the connector skills in this catalog whose serviceId is mapped to a unified API.
Send any HTTP request to https://unify.apideck.com/proxy. Apideck looks up the user's stored Azure DevOps credentials by x-apideck-consumer-id + x-apideck-service-id, injects them on the way out, and returns Azure DevOps's raw response.
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: azure-devops" \
-H "x-apideck-downstream-url: <target endpoint on Azure DevOps>" \
-H "x-apideck-downstream-method: GET"
For POST/PATCH/PUT/DELETE, change x-apideck-downstream-method and pass the body as you would to Azure DevOps directly. Apideck does not transform the body — it forwards bytes.
See Azure DevOps's API docs for available endpoints.
apideck-rest — REST patterns including the Proxyapideck-best-practices — Vault, error handling, retriesapideck-unified-api — when to use unified vs proxyAccess Financials integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Access Financials. Routes through Apideck with serviceId "access-financials".
Acerta integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Acerta. Routes through Apideck with serviceId "acerta".
Act integration via Apideck's CRM unified API — same methods work across every connector in CRM, switch by changing `serviceId`. Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in Act. Routes through Apideck with serviceId "act".
ActiveCampaign integration via Apideck's CRM unified API — same methods work across every connector in CRM, switch by changing `serviceId`. Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in ActiveCampaign. Routes through Apideck with serviceId "activecampaign".
Acumatica integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Acumatica. Routes through Apideck with serviceId "acumatica".
ADP iHCM integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in ADP iHCM. Routes through Apideck with serviceId "adp-ihcm".