WebApps API Client

Name: WebApps API Client API
Brand: WebApps API Client
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth2349 EndpointsREST

For Agents

Provision, configure, deploy, and operate Azure App Service web apps, function apps, and deployment slots through the Azure Resource Manager control plane.

Connect the WebApps API Client to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WebApps 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.

Install Jentic One Beta (Self-Hosted)

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

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 WebApps API Client API.

Provision App Service web apps, function apps, and API apps in any region under a subscription

Manage deployment slots and perform slot swaps for blue-green releases

Configure app settings, connection strings, and runtime configuration without redeploying

Bind custom hostnames and SSL certificates to a site for production traffic

GET STARTED

Start building with WebApps API Client API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for WebApps API Client, keeping it validated and agent-ready.

The Azure WebApps API Client is the management plane for Azure App Service web apps, function apps, and API apps. It exposes 349 operations across 252 resource paths under the Microsoft.Web/sites provider, covering site lifecycle, deployment slots, configuration, app settings, custom hostnames, SSL bindings, source control, backups, scaling, host name bindings, and diagnostics. Use it to script the full lifecycle of an App Service site, from creation and configuration through to backup, slot swaps, and decommissioning.

Use Cases

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

★ Blue-green releases with slot swaps

Deploy new application versions to a staging deployment slot, run smoke tests, then perform a slot swap into production using the WebApps slot endpoints. The API exposes the full slot lifecycle so an automation runner can promote builds without downtime, and rolls back simply by swapping again.

Swap the staging slot into production for site app-checkout-prod in resource group prod-rg and confirm the long-running operation completes.

Bulk configuration of App Service apps

Iterate over every web app in a subscription and apply standardised app settings, connection strings, or always-on flags. The list-by-subscription and update-application-settings endpoints make it possible to enforce platform policy across hundreds of sites in a single automation run, instead of clicking through the portal.

List all web apps in resource group prod-rg and update each one to set httpsOnly=true and minTlsVersion=1.2.

Custom domain and TLS automation

Add a verified custom hostname to an App Service site, attach an uploaded SSL certificate, and turn on HTTPS-only mode. The hostNameBindings and sslStates endpoints let agents take a domain from request to live TLS in a scripted workflow, with verification calls to check DNS readiness before binding.

Bind hostname checkout.example.com to site app-checkout-prod, attach the existing SSL certificate, and set httpsOnly to true.

Agent-driven App Service operations

Let an AI agent restart hung sites, retrieve diagnostic logs, and check site health through Jentic-mediated calls to the WebApps API. Surface common ops actions as agent tools so on-call engineers can ask the agent to act instead of chasing portal links.

Search Jentic for 'restart azure app service web app', load the operation schema, and execute it for site app-checkout-prod in resource group prod-rg.

Key Endpoints

349 endpoints — the azure webapps api client is the management plane for azure app service web apps, function apps, and api apps.

METHOD

PATH

DESCRIPTION

GET

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

List all web apps in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites

List web apps in a resource group

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}

Get a web app by name

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/applySlotConfig

Apply slot configuration to a site

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/backup

Trigger an on-demand backup

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/analyzeCustomHostname

Validate a custom hostname before binding

GET

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

List all web apps in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites

List web apps in a resource group

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}

Get a web app by name

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/applySlotConfig

Apply slot configuration to a site

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/backup

Trigger an on-demand backup

Why though Jentic?

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

Credential isolation

Azure AD OAuth tokens for `azure_auth` are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped, short-lived bearer tokens — refresh tokens and client secrets never enter the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'restart an azure web app') and Jentic returns the matching WebApps operation with its full input schema, so the agent can call the right ARM endpoint without browsing through 349 spec entries.

Time to first call

Direct integration: 2-5 days to handle Azure AD auth, ARM polling, and the breadth of 349 operations. Through Jentic: under 1 hour — search by intent, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

App Service Plans API Client

Manage the App Service plan that hosts web apps

Call App Service Plans first to provision the compute plan, then use WebApps to create sites on top of it.

Complementary

App Service Environments API Client

Manage isolated, single-tenant App Service Environments

Use ASE when isolation, VNet integration, or higher scale is required for the apps managed by WebApps.

Alternative

Deleted Web Apps API Client

Inspect and restore web apps that have been deleted

Use the Deleted Web Apps API for recovery scenarios; use WebApps for live site lifecycle.

FAQs

Specific to using WebApps API Client API through Jentic.

What authentication does the WebApps API Client use?

The API uses Azure Active Directory OAuth 2.0 via the implicit flow scheme `azure_auth`, scoped to user_impersonation against https://management.azure.com. Through Jentic the OAuth token stays in the vault and only short-lived scoped bearer tokens are exposed to the agent.

Can I swap deployment slots with this API?

Yes. The applySlotConfig and slotsswap operations under /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name} support promoting a staging slot into production as a long-running operation. Poll the returned operation URL until it reports succeeded.

What are the rate limits for the WebApps API?

The spec does not declare explicit rate limits. Calls go through Azure Resource Manager, which enforces standard ARM throttling per subscription and per region. Read the x-ms-ratelimit-remaining-subscription-reads and -writes headers to track quota.

How do I list every web app in my subscription through Jentic?

Search Jentic for 'list azure app service web apps', load the schema for GET /subscriptions/{subscriptionId}/providers/Microsoft.Web/sites, and execute it. Install with `pip install jentic` and use the async search/load/execute pattern.

Can this API deploy my application code?

Indirectly. The API configures source control integration via the sourcecontrols endpoints and manages deployment slots, but it does not push code itself. Code is published via Git, container registry pulls, ZIP deploy, or run-from-package — the WebApps API arranges the configuration around those flows.

Does this API manage App Service Plans?

No. App Service Plans (the underlying compute SKU and scale unit) are managed by the separate appserviceplans-api-client API. Use this WebApps API for sites and slots, and the App Service Plans API for the plan they run on.