Mock sample for your project: SubscriptionClient API

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

SubscriptionClient

azure.com

Version: 2018-03-01-preview


Use this API in your project

Speed up your application development by using "SubscriptionClient 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

Subscription client provides an interface to create and manage Azure subscriptions programmatically.

Other APIs by azure.com

Microsoft.Support

azure.com
Microsoft Azure Support Resource Provider.

QnAMaker Client

azure.com
An API for QnAMaker Service

ApplicationInsightsManagementClient

azure.com
Azure Application Insights client for web test based alerting.

ApiManagementClient

azure.com
Use these REST APIs for performing operations on OpenId Connect Provider entity associated with your Azure API Management deployment. API Management allows you to access APIs secured with token from OpenID Connect Provider to be accessed from the Developer Console.

ApplicationInsightsManagementClient

azure.com
Azure Application Insights client for saved items.

ApiManagementClient

azure.com
Use these REST APIs for performing operations on Certificate entity in your Azure API Management deployment. Certificates can be used to setup mutual authentication with your Backend in API Management. For more information refer to How to secure backend using Mutual Auth Certificate.

Azure Alerts Management Service Resource Provider

azure.com
Azure Alerts Management Service provides a single pane of glass of alerts across Azure Monitor.

ApplicationInsightsManagementClient

azure.com
Azure Application Insights client for web test based alerting.

AutomationManagement

azure.com

FabricAdminClient

azure.com
Fabric location operation endpoints and objects.

ApplicationInsightsManagementClient

azure.com
Azure Application Insights client for selecting pricing plans and options.

Azure Log Analytics Query Packs

azure.com
Azure Log Analytics API reference for Query Packs management.

Other APIs in the same category

AzureBridgeAdminClient

azure.com
AzureBridge Admin Client.

SearchIndexClient

azure.com
Client that can be used to query an index and upload, merge, or delete documents.

Amazon Personalize Runtime

FabricAdminClient

azure.com
MAC address pool operation endpoints and objects.

Amazon Kinesis Analytics

Amazon Kinesis Analytics Overview This documentation is for version 1 of the Amazon Kinesis Data Analytics API, which only supports SQL applications. Version 2 of the API supports SQL and Java applications. For more information about version 2, see Amazon Kinesis Data Analytics API V2 Documentation. This is the Amazon Kinesis Analytics v1 API Reference. The Amazon Kinesis Analytics Developer Guide provides additional information.

Amazon Kinesis Analytics

Amazon Kinesis Data Analytics is a fully managed service that you can use to process and analyze streaming data using Java, SQL, or Scala. The service enables you to quickly author and run Java, SQL, or Scala code against streaming sources to perform time series analytics, feed real-time dashboards, and create real-time metrics.

ApiManagementClient

azure.com
Use these REST APIs for performing operations on Quota entity associated with your Azure API Management deployment. To configure call rate limit and quota policies refer to how to configure call rate limit and quota.

AWS Elemental MediaPackage VOD

AWS Elemental MediaPackage VOD

Application Insights Data Plane

This API exposes AI metric & event information and associated metadata

AutomationManagement

azure.com

AWS DataSync

DataSync DataSync is a managed data transfer service that makes it simpler for you to automate moving data between on-premises storage and Amazon Simple Storage Service (Amazon S3) or Amazon Elastic File System (Amazon EFS). This API interface reference for DataSync contains documentation for a programming interface that you can use to manage DataSync.

Amazon Route 53 Resolver

When you create a VPC using Amazon VPC, you automatically get DNS resolution within the VPC from Route 53 Resolver. By default, Resolver answers DNS queries for VPC domain names such as domain names for EC2 instances or Elastic Load Balancing load balancers. Resolver performs recursive lookups against public name servers for all other domain names. You can also configure DNS resolution between your VPC and your network over a Direct Connect or VPN connection: Forward DNS queries from resolvers on your network to Route 53 Resolver DNS resolvers on your network can forward DNS queries to Resolver in a specified VPC. This allows your DNS resolvers to easily resolve domain names for Amazon Web Services resources such as EC2 instances or records in a Route 53 private hosted zone. For more information, see How DNS Resolvers on Your Network Forward DNS Queries to Route 53 Resolver in the Amazon Route 53 Developer Guide. Conditionally forward queries from a VPC to resolvers on your network You can configure Resolver to forward queries that it receives from EC2 instances in your VPCs to DNS resolvers on your network. To forward selected queries, you create Resolver rules that specify the domain names for the DNS queries that you want to forward (such as example.com), and the IP addresses of the DNS resolvers on your network that you want to forward the queries to. If a query matches multiple rules (example.com, acme.example.com), Resolver chooses the rule with the most specific match (acme.example.com) and forwards the query to the IP addresses that you specified in that rule. For more information, see How Route 53 Resolver Forwards DNS Queries from Your VPCs to Your Network in the Amazon Route 53 Developer Guide. Like Amazon VPC, Resolver is Regional. In each Region where you have VPCs, you can choose whether to forward queries from your VPCs to your network (outbound queries), from your network to your VPCs (inbound queries), or both.