Block Subscription to an API

An API publisher blocks subscription to an API as a way of disabling access to it and managing its usage and /wiki/spaces/AM260/pages/30901444. A subscription blocking can be temporary or permanent. There is an unblocking facility to allow API invocations back.

You block APIs by subscriptions. That is, a given user is blocked access to a given API that s/he has subscribed to using a given application. If a user is subscribed to two APIs using the same application and you block access to only one of the APIs, s/he can still continue to invoke the other APIs that s/he subscribed to using the same application. Also, s/he can continue to access the same API subscribed to using different applications.

API level subscription blocking is useful to control only the subscriptions created for a specific API by a user. If you want to block all API requests from a specific application/user/specific IP address or to a specific API, you can use request blacklisting.

Blocking can be done at two levels:

Block production and sandbox access: API access is blocked with both production and sandbox keys.
Block production access only: Allows sandbox access only. This is useful when you want to fix and test an issue in an API. Rather than blocking all access, you can block production access only, allowing the developer to fix and test it.

When API Gateway caching is enabled (it is enabled by default), even after blocking a subscription, consumers might still be able to access APIs until the cache expires, which happens approximately every 15 minutes. Likewise, the API Gateway cache applies even when an API is unblocked.

See the following topics for the descriptions on the concepts that you need to know when you block subscriptions to an API:

Create two APIs.
1. Sign in to the WSO2 API Publisher.
2. Create two APIs by the names TestAPI1 and TestAPI2 and publish them to the WSO2 API Store.
  For more information, see Create and Publish an API.
Subscribe to both the APIs.
1. Sign in to the WSO2 API Store and click APIS.
  Note that the two APIs are visible in the APIs page.
2. Subscribe to both APIs using the same application.
  You can use the default application or create your own.
3. Click the View Subscriptions button when prompted.
  The Subscriptions tab opens.
4. Click the Production Keys tab and click Generate Keys to create an application access token.
  If you have already generated an access token before, click Re-generate to renew the token.
Invoke both APIs using the access token you received in the previous step.

You have subscribed to two APIs and invoked them successfully. Let's block one subscription and see the outcome.
Block an API.
1. Sign back in to the API Publisher.
2. Click API and click on the API that you need to block.
  In this case, click on the TestAPI1 API.
3. Click Subscriptions to navigate to the managed subscription section.
4. Click Block.
  Note that the Block link immediately turns to Unblock, allowing you to activate the subscription back at any time.
Invoke the APIs to test the blocked API.
1. Sign back in to the API Store.
2. Invoke the two APIs (TestAPI1 and TestAPI2) again as mentioned in step 3.
  
  You might have to regenerate the access token for the respective application that you subscribed the APIs to (for example in this case it will be DefaultApplication) if the access token expiration time (1 hour by default) has passed since the last time you generated it.
  Note that you can invoke TestAPI2 again, but when you invoke TestAPI1, it gives a message that the requested API is temporarily blocked. Neither the API publisher nor any subscriber can invoke the API until the block is removed.
  
  When Gateway caching is enabled, which is the case by default, the subscription blocking will take place only after the token cache expires (the default token cache expiry time is 15min). However, if the token is regenerated after the API is blocked, then the API will be blocked immediately.
  Response when invoking TestAPI1
```
<ams:fault xmlns:ams="http://wso2.org/apimanager/security">
   <ams:code>900907</ams:code>
   <ams:message>The requested API is temporarily blocked</ams:message>
   <ams:description>Access failure for API: /TestAPI1/1.0.0, version: 1.0.0 status: (900907) - The requested API is temporarily blocked</ams:description>
</ams:fault>
```
If you click Applications in the API Store, and select the application that you used to subscribe to the API, the details of the blocked subscription appears.
Unblock the API.
1. Go back to the API Publisher.
2. Click on the respective API
  In this case click TestAPI1 1.0.0.
3. Click Subscriptions and click Unblock corresponding to the respective subscription.
  Make sure to click on the subscription that corresponds to the correct Application.
If you invoke TestAPI1 again, you will notice that you can invoke the API as usual.

When Gateway caching is enabled, which is the case by default, the subscription unblocking will take place only after the token cache expires (the default token cache expiry time is 15min). However, if the token is regenerated after the API is unblocked, then the API will be unblocked immediately.

You have subscribed to two APIs, blocked subscription to one and tested that you cannot invoke the blocked API.