Microsoft Azure

Azure API Management: Apimgateway Config Connections

Use these REST APIs to manage Azure API Management gateway config connections deployments.

Developer tools#openapi

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

Use these REST APIs to manage Azure API Management gateway config connections deployments.

Endpoints 4

ApiGatewayConfigConnection

  • GETApiGatewayConfigConnection_ListByGateway/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.ApiManagement/gateways/:gatewayName/configConnectionsList all API Management gateway config connections within a gateway.
  • GETApiGatewayConfigConnection_Get/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.ApiManagement/gateways/:gatewayName/configConnections/:configConnectionNameGets an API Management gateway config connection resource description.
  • PUTApiGatewayConfigConnection_CreateOrUpdate/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.ApiManagement/gateways/:gatewayName/configConnections/:configConnectionNameCreates or updates an API Management gateway config connection. This is long running operation and could take several minutes to complete.
  • DELETEApiGatewayConfigConnection_Delete/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.ApiManagement/gateways/:gatewayName/configConnections/:configConnectionNameDeletes an existing API Management gateway config connection.

API details

Base URL
https://management.azure.com
Authentication
OAuth 2.0 (implicit flow) with 1 scope
Operations
4 operations on 2 pathsGET 2PUT 1DELETE 1
Main resources
ApiGatewayConfigConnection 4
Response formats
application/json
Description format
Swagger 2.0, API version 2024-05-01

How to test the Azure API Management: Apimgateway Config Connections in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Azure API Management: Apimgateway Config Connections collection, without the publisher's secrets.
  3. Add your credentialsThis API uses OAuth 2.0 (implicit flow) with 1 scope. Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “ApiGatewayConfigConnection_ListByGateway” (GET /subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.ApiManagement/gateways/:gatewayName/configConnections), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Azure API Management: Apimgateway Config Connections?

Use these REST APIs to manage Azure API Management gateway config connections deployments. It is listed under Developer tools and has 4 endpoints.

Who publishes the Azure API Management: Apimgateway Config Connections?

It is listed from Microsoft Azure's public API description (an OpenAPI document), not published by Microsoft Azure on Swastik Codes. Anyone who controls azure.com can claim the profile by adding a DNS TXT record.

What is the base URL of the Azure API Management: Apimgateway Config Connections?

Requests go to https://management.azure.com. Endpoint paths are added to this base URL.

How do I authenticate with the Azure API Management: Apimgateway Config Connections?

With OAuth 2.0 (implicit flow) with 1 scope.

How many endpoints does the Azure API Management: Apimgateway Config Connections have?

4 operations on 2 paths (2 GET, 1 PUT, 1 DELETE). The largest groups are ApiGatewayConfigConnection.

Is forking the Azure API Management: Apimgateway Config Connections free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.