Microsoft Azure

Azure Azurestackhci: Network Interfaces

The Microsoft.AzureStackHCI Rest API spec.

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

The Microsoft.AzureStackHCI Rest API spec.

Endpoints 6

  • GETNetworkInterfaces_Get/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.AzureStackHCI/networkInterfaces/:networkInterfaceNameGets a network interface
  • PUTNetworkInterfaces_CreateOrUpdate/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.AzureStackHCI/networkInterfaces/:networkInterfaceNameThe operation to create or update a network interface. Please note some properties can be set only during network interface creation.
  • DELETENetworkInterfaces_Delete/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.AzureStackHCI/networkInterfaces/:networkInterfaceNameThe operation to delete a network interface.
  • PATCHNetworkInterfaces_Update/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.AzureStackHCI/networkInterfaces/:networkInterfaceNameThe operation to update a network interface.
  • GETNetworkInterfaces_List/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.AzureStackHCI/networkInterfacesLists all of the network interfaces in the specified resource group. Use the nextLink property in the response to get the next page of network interfaces.
  • GETNetworkInterfaces_ListAll/subscriptions/:subscriptionId/providers/Microsoft.AzureStackHCI/networkInterfacesLists all of the network interfaces in the specified subscription. Use the nextLink property in the response to get the next page of network interfaces.

API details

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

How to test the Azure Azurestackhci: Network Interfaces 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 Azurestackhci: Network Interfaces 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 “NetworkInterfaces_Get” (GET /subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.AzureStackHCI/networkInterfaces/:networkInterfaceName), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Azure Azurestackhci: Network Interfaces?

The Microsoft.AzureStackHCI Rest API spec. It is listed under Developer tools and has 6 endpoints.

Who publishes the Azure Azurestackhci: Network Interfaces?

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 Azurestackhci: Network Interfaces?

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

How do I authenticate with the Azure Azurestackhci: Network Interfaces?

With OAuth 2.0 (implicit flow) with 1 scope.

How many endpoints does the Azure Azurestackhci: Network Interfaces have?

6 operations on 3 paths (3 GET, 1 PUT, 1 PATCH, 1 DELETE).

Is forking the Azure Azurestackhci: Network Interfaces 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.