Microsoft Azure LogicAppsManagementClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureServerlessoauth226 EndpointsREST
For Agents
Manage Azure Logic Apps connectors, on-premises connection gateways, and custom API definitions through Azure Resource Manager. Use for connector and gateway lifecycle, not for executing Logic App workflows.
Use for: Set up an on-premises data gateway so my Logic App can reach a SQL Server inside the corporate network, List all managed APIs available to Logic Apps in the West Europe region, Register a custom Logic Apps connector from this SOAP endpoint's WSDL, Find all connection gateways I administer across subscriptions
Not supported: Does not execute workflows, manage workflow runs, or trigger Logic Apps — use only for managing connectors, gateways, and custom API definitions in the Microsoft.Web connector plane.
Jentic publishes the only available OpenAPI specification for LogicAppsManagementClient, keeping it validated and agent-ready. LogicAppsManagementClient is the Azure Resource Manager surface for the connector and gateway plane behind Azure Logic Apps. It manages on-premises connection gateways, the catalog of managed APIs available to Logic Apps, custom API definitions extracted from WSDL or Swagger, and connection objects that bind a Logic App to an external system. It does not run workflows or trigger Logic App executions.
Install Jentic One Beta
Connect the LogicAppsManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LogicAppsManagementClient, 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.
1
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 | sh2
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 instanceJentic 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 LogicAppsManagementClient API.
Provision and configure on-premises connection gateways for hybrid Logic App scenarios
Browse the catalog of managed APIs (Salesforce, SQL, SharePoint, etc.) available to Logic Apps in a region
Register custom API definitions by extracting them from WSDL endpoints or Swagger documents
List installed connection gateways an administrator owns across regions
Manage Logic App connection objects that bind a workflow to a specific external system credential
Inspect WSDL interfaces before importing them as a custom Logic Apps connector
Use Cases
Patterns agents use LogicAppsManagementClient API for, with concrete tasks.
★ Hybrid Connectivity for Logic Apps
Enterprises running Logic Apps that need to read from on-premises SQL Server, SAP, or file shares require an installed on-premises data gateway. LogicAppsManagementClient surfaces the gateway lifecycle — listing installed gateways the user administers, fetching gateway details, and exposing connection gateway resources for Logic App workflows to bind to. Combined with the Logic Apps designer, this enables hybrid integration without exposing internal services to the public internet.
List the connection gateway installations the current admin owns in westeurope, then return the gateway with displayName 'corp-gw-01' so a workflow connection can be bound to it.
Custom Connector Onboarding
Integration teams expose internal SOAP services as Logic Apps custom connectors by extracting an API definition from a published WSDL. The extractApiDefinitionFromWsdl operation returns a Swagger document derived from the WSDL, which can then be POSTed back to register a custom API resource. This shortens custom-connector onboarding from a manual half-day exercise to a single API call.
POST to /providers/Microsoft.Web/locations/{location}/extractApiDefinitionFromWsdl with the partner's WSDL URL, then create a customApi resource using the returned Swagger document.
Connector Catalog Discovery
Solution architects designing Logic App workflows need to know which managed connectors are available in a target region — Microsoft adds new connectors and gates some by region. Listing managedApis at /providers/Microsoft.Web/locations/{location}/managedApis returns the full catalog with display names and the connection parameters each connector requires, so an agent can plan workflow design before opening the designer.
GET /subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/eastus/managedApis and return the list of connector display names that include 'Salesforce' or 'Dynamics'.
AI Agent Logic Apps Integration Setup
AI agents that build integrations through Logic Apps use Jentic to discover the connector and gateway management surface. The agent searches for an intent, Jentic returns the matching ARM operation, and the agent executes the call to register custom APIs or bind connection gateways without writing direct ARM client code.
Search Jentic for 'register a custom logic apps connector', load the customApi creation schema, and POST the converted Swagger to register the connector under the target resource group.
Key Endpoints
26 endpoints — jentic publishes the only available openapi specification for logicappsmanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Web/connectionGateways
List all connection gateways in a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Web/customApis
List custom API connectors
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/managedApis
List managed connector catalog for a region
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/extractApiDefinitionFromWsdl
Convert a WSDL into a Swagger API definition
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/listWsdlInterfaces
List interfaces inside a WSDL
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/managedApis/{apiName}
Get a single managed connector definition
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Web/connectionGateways
List all connection gateways in a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Web/customApis
List custom API connectors
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/managedApis
List managed connector catalog for a region
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/extractApiDefinitionFromWsdl
Convert a WSDL into a Swagger API definition
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/listWsdlInterfaces
List interfaces inside a WSDL
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Web/locations/{location}/managedApis/{apiName}
Get a single managed connector definition
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AAD client credentials live encrypted in the Jentic vault and a short-lived bearer token for management.azure.com is injected at call time. Connection-level credentials registered into Logic Apps connections also benefit from Jentic's isolation — secrets never appear in agent prompts or logs.
Intent-based discovery
Agents search by intent (for example, 'extract logic apps connector from wsdl') and Jentic returns the corresponding ARM operation with its full input schema, so the agent calls the correct endpoint without scraping Microsoft Docs.
Time to first call
Direct ARM integration for connector lifecycle: 2-3 days for AAD setup, retry handling, and WSDL parsing wrappers. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using LogicAppsManagementClient API through Jentic.
Why is there no official OpenAPI spec for LogicAppsManagementClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call LogicAppsManagementClient 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 LogicAppsManagementClient use?
Azure Active Directory OAuth 2.0 bearer tokens scoped to the management.azure.com audience. With Jentic, the AAD client secret stays in the encrypted vault — agents receive only short-lived scoped tokens at call time.
Can I trigger a Logic App run with this API?
No. Workflow run, trigger, and history operations live in the Microsoft.Logic provider (LogicManagementClient), not Microsoft.Web. This client manages the connector, gateway, and custom API plane only.
What are the rate limits for the LogicAppsManagementClient?
Standard Azure Resource Manager throttling applies — typically 12,000 reads and 1,200 writes per hour per subscription per region. ARM responds with 429 and a Retry-After header when exceeded.
How do I register a custom Logic Apps connector through Jentic?
Run pip install jentic, then search Jentic for 'register a custom logic apps connector'. Jentic returns the extractApiDefinitionFromWsdl operation followed by the customApi creation schema — the agent loads both, converts the WSDL, then POSTs the resulting Swagger to register the connector.
Where do I configure the on-premises data gateway runtime?
The gateway runtime is installed on a Windows machine inside your network using Microsoft's downloadable installer; this API only manages the cloud-side connectionGateways resource and reports installation status. The endpoint /providers/Microsoft.Web/locations/{location}/connectionGatewayInstallations lists installations the current admin owns.
GET STARTED