Admin API

ADO Pilot has no public admin API in v1. This page outlines the deferred public API roadmap for v2.

Last updated

View as Markdown

ADO Pilot does not ship a public admin API in v1. Administrative operations like quota adjustments and webhook rotations are internal-only tooling used by the ADO Pilot operations team, and aren't exposed as an API you can call directly. (Manual re-review is different — you can already trigger one yourself from the PR action menu or the Settings Hub; see Re-running a review.)

If you need an administrative action today that isn't surfaced in the dashboard, open a support request and we'll perform it on your behalf.

v1 status

The dashboard already covers the day-to-day administrative needs most teams have:

If a workflow you need is missing, the items below describe what we're considering for v2.

Deferred to v2

The public admin API is on the post-v1 roadmap. We expect to ship it after the v1 launch stabilizes; the exact timing is still being scoped. The current candidate scope is:

  • API access to manual review retry. Programmatically trigger a re-review of an existing PR (and optionally, a write-back-only mode that re-posts the prior verdict without consuming a new review credit) — the same action already available from the PR action menu and Settings Hub, but callable from your own scripts.
  • Quota adjustments. Programmatically set or clear an overage cap, grant emergency review credits, or pause billing for a tenant.
  • Webhook health & re-provision. Inspect the state of each service hook subscription, force a fresh webhook credential, and re-create a missing or broken subscription.
  • Review history export. Bulk-export review records (verdicts, findings, RC consumption) for a billing period for audit and reporting.
  • Tenant-scoped authentication. OAuth client-credentials grants tied to your ADO Pilot organization, scoped to admin actions on that tenant only.
  • Versioned, stable contract. A documented OpenAPI specification and a semver guarantee on the API surface — none of which the internal endpoints offer today.

If any of these are blocking you, let us know via a support request. Customer demand directly shapes the v2 priority list.