Microsoft Azure LogicAppsManagementClient

Name: LogicAppsManagementClient API
Brand: LogicAppsManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureServerlessoauth226 Endpoints

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.

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 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

GET STARTED

Start building with LogicAppsManagementClient API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

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

Credential isolation

Your Azure AD credential for the Logic Apps control plane is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Logic Apps managed connectors' or 'read a custom Logic Apps connector', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Microsoft Azure Logic Apps Management API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, so you can allow it to only list connection gateways, custom APIs, and managed APIs while withholding anything else. Since this API puts the managed API in the URL path, such as /locations/{location}/managedApis/{apiName}, you can pin the agent to reading connectors and managed APIs within a single location. Write actions like extracting an API definition from a WSDL are excluded unless you explicitly add them to what the agent is permitted to call.

Microsoft Azure LogicAppsManagementClient

Connect the LogicAppsManagementClient to your agent

Capabilities

Start building with LogicAppsManagementClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs