Microsoft Azure DeletedWebApps API Client

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth23 EndpointsREST

For Agents

List soft-deleted Azure App Service web apps at subscription or region scope and look up the metadata of a specific deleted site.

Install Jentic One Beta

Connect the DeletedWebApps API Client to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DeletedWebApps API Client, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with DeletedWebApps API Client API.

List all soft-deleted web apps in a subscription

List soft-deleted web apps in a specific Azure region

Retrieve the metadata of a specific deleted web app by location and deletedSiteId

GET STARTED

Start building with DeletedWebApps API Client API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use DeletedWebApps API Client API for, with concrete tasks.

★ Accidental deletion recovery

When an engineer deletes the wrong App Service app, the recovery path begins by enumerating soft-deleted sites in the affected subscription or region. The deleted web apps endpoints expose every recoverable site with the original resource group and deletion timestamp so the operator can identify the right deletedSiteId before triggering a restore.

List deleted web apps in West Europe deleted in the last 24 hours and return the deletedSiteId, original resource group, and deletion timestamp for each

Deletion audit

A platform team wants a regular report of which App Service apps have been deleted across the subscription. The list endpoints provide the source data; combined with timestamps and original resource group names, the report tracks deletion velocity and flags unexpected losses for review.

Generate a CSV of every web app deleted in the subscription in the past 7 days with location, original resource group, and deletion time

Pre-restore validation

Before launching a restore, an operator confirms the deleted site exists, is in the expected region, and references the expected resource group. The per-site GET endpoint returns the full deleted-site descriptor so the restore controller can validate input parameters before issuing a long-running restore call against a separate App Service API.

Look up the deleted site with deletedSiteId '12345' in West Europe and confirm its original resource group matches 'production-rg'

Agent-driven recovery triage

An on-call AI agent receives an alert that a critical App Service app is missing. Through Jentic the agent searches for deleted-webapp listing operations, narrows the result by region and timestamp, and identifies the candidate deletedSiteId so a human or downstream restore tool can act with confidence.

Search for any web app named 'orders-prod' deleted in the past 6 hours across the subscription and return its deletedSiteId and location

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for deletedwebapps api client, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Web/deletedSites

List all deleted web apps in a subscription

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/deletedSites

List deleted web apps in a specific region

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/deletedSites/{deletedSiteId}

Get a specific deleted web app by location and deletedSiteId

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Web/deletedSites

List all deleted web apps in a subscription

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/deletedSites

List deleted web apps in a specific region

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/deletedSites/{deletedSiteId}

Get a specific deleted web app by location and deletedSiteId

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure AD OAuth 2.0 client credentials are stored encrypted in the Jentic vault. Agents receive a scoped bearer token at execute time; client secrets and refresh tokens never reach the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'list deleted azure web apps') and Jentic returns the right deletedSites listing operation with the subscription and location parameters surfaced from the spec.

Time to first call

Direct integration with Azure Resource Manager for deleted-site listing, including AAD setup, typically takes a few hours. Through Jentic: under 30 minutes to first successful list call.

FAQs

Specific to using DeletedWebApps API Client API through Jentic.

Why is there no official OpenAPI spec for DeletedWebApps API Client?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DeletedWebApps API Client via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Deleted Web Apps API use?

The API is part of Azure Resource Manager and uses OAuth 2.0 bearer tokens issued by Azure Active Directory. Through Jentic, the AAD client secret or managed identity refresh token is held in the encrypted vault and a short-lived access token is supplied at execute time so the bearer token never appears in the agent's context.

Can I list deleted App Service apps in a single region with this API?

Yes. GET /subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/deletedSites returns every soft-deleted web app in the named region. Pair the result with the per-site GET to retrieve the original resource group and deletion timestamp before initiating a restore elsewhere in App Service.

What are the rate limits for the Deleted Web Apps API?

Azure Resource Manager applies subscription-level read throttles (around 12,000 reads per hour per region per subscription) and returns 429 with a Retry-After header when exceeded. The three endpoints in this API are read-only, so the read quota is the relevant ceiling.

How do I find a specific deleted web app through Jentic?

Search Jentic for 'list deleted azure web apps in region', load the schema for GET /subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/deletedSites, then execute with your subscriptionId and the target location. The pip install jentic Python SDK uses the async search, load, execute pattern.

Is the Deleted Web Apps API free?

There is no per-call charge for the management API; Azure does not bill listing or reading deleted-site metadata. Restoration of a deleted app, performed through a separate App Service operation, may consume App Service Plan capacity once the app is brought back.