Scenario: Allow only 5 properties within a JSON object
Scenario: Allow only 5 properties within a JSON object
Scenario: In this exercise, we will see how to use flow variables.
Scenario: Suppose you want to apply Spike Arrest policy based on Client
Scenario: You want to pass the quota available count and quota used count in response
Scenario: You want to send custom message using fault rules in case of Quota error
Scenario: You want to assign different quotas based on client application
Scenario: You want to start the counter for the Quota policy when the 1st request is received.
Scenario: You want to activate quota policy using rolling window type. In this case, counter will not be reset after particular interval of time.
Scenario: You want to activate quota policy from a particular datetime.
Scenario: You want to limit API calls/time interval based on message weight.
Scenario: You want to limit API calls based on time interval for each client application
Scenario: Suppose your backend system can handle 2 request per minute.
Scenario: Instead of hitting your backend server multiple times, you want to cache the response for the data which is not updated frequently.
Scenario: You want to provide access to API using API Key.
Scenario: You want to limit API calls based on time interval.
Scenario: Client always wants response in XML format. Now, if client sends GET request to /json path, target system sends a JSON response. So, there should be a conversion rule to convert JSON to XML before sending response back to the client.
Scenario: While sending the request, Client sends the search parameter in the form of query but Back-end system excepts it as a header parameter
Scenario: Target system returns the response in XML format. But Client wants the response in JSON format.
Scenario: Target system returns the response in JSON format. But Client wants the response in XML format.