Mock sample for your project: FeatureClient API

Integrate with "FeatureClient API" from azure.com in no time with Mockoon's ready to use mock sample

FeatureClient

azure.com

Version: 2015-12-01


Use this API in your project

Speed up your application development by using "FeatureClient API" ready-to-use mock sample. Mocking this API will allow you to start working in no time. No more accounts to create, API keys to provision, accesses to configure, unplanned downtime, just work.
It also improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.

Description

Azure Feature Exposure Control (AFEC) provides a mechanism for the resource providers to control feature exposure to users. Resource providers typically use this mechanism to provide public/private preview for new features prior to making them generally available. Users need to explicitly register for AFEC features to get access to such functionality.

Other APIs by azure.com

Cosmos DB

azure.com
Azure Cosmos DB Database Service Resource Provider REST API

RedisManagementClient

azure.com
REST API for Azure Redis Cache Service.

AutomationManagement

azure.com

FabricAdminClient

azure.com
MAC address pool operation endpoints and objects.

FabricAdminClient

azure.com
Logical network operation endpoints and objects.

InfrastructureInsightsManagementClient

azure.com
Region health operation endpoints and objects.

FabricAdminClient

azure.com
Network operation results.

GalleryManagementClient

azure.com
The Admin Gallery Management Client.

BackupManagementClient

azure.com
The Admin Backup Management Client.

FabricAdminClient

azure.com
Software load balancer multiplexer operation endpoints and objects.

Compute Admin Client

azure.com

DeploymentAdminClient

azure.com
Deployment Admin Client.

Other APIs in the same category

ContainerRegistryManagementClient

azure.com

Azure Activity Log Alerts

azure.com

RecoveryServicesClient

azure.com

Amazon Lex Runtime Service

Amazon Lex provides both build and runtime endpoints. Each endpoint provides a set of operations (API). Your conversational bot uses the runtime API to understand user utterances (user input text or voice). For example, suppose a user says "I want pizza", your bot sends this input to Amazon Lex using the runtime API. Amazon Lex recognizes that the user request is for the OrderPizza intent (one of the intents defined in the bot). Then Amazon Lex engages in user conversation on behalf of the bot to elicit required information (slot values, such as pizza size and crust type), and then performs fulfillment activity (that you configured when you created the bot). You use the build-time API to create and manage your Amazon Lex bot. For a list of build-time operations, see the build-time API, .

AutomationManagement

azure.com

DataBoxEdgeManagementClient

azure.com

NetworkManagementClient

azure.com
The Microsoft Azure Network management API provides a RESTful set of web services that interact with Microsoft Azure Networks service to manage your network resources. The API has entities that capture the relationship between an end user and the Microsoft Azure Networks service.

Managed Streaming for Kafka Connect

AzureDigitalTwinsManagementClient

azure.com
Azure Digital Twins Client for managing DigitalTwinsInstance

ContainerServiceClient

azure.com
The Container Service Client.

RecoveryServicesClient

azure.com

Microsoft NetApp

azure.com
Microsoft NetApp Azure Resource Provider specification