Switch to daily quotas.

Disable quota evaluation for chained proxies.

Increase quota levels in API Product settings

Use Analytics reports to balance proxy queries

a value that expires after 300 seconds

OAuth tokens for backend service calls

configuration values

an HTTP response

Add custom attributes for counts for every product. Create custom quota policies for every product which references these custom attributes

Set custom attributes for weekday and weekend count at every product Reference these How variables in the count property of Quota policy at runtime

Add custom attributes at the API Product with counts to use for weekdays and weekends. Using flow variables, reference the custom counts in the Quota policy

Add custom attributes for count at Product level Use a JS Policy to determine which count to use in Quota policy at runtime Use this count attribute in the Quota Policy.

The internet latency

The network latency

The backend latency

The Apigee proxy latency

The backend database latency

GET

PUT

POST

DELETE

OPTIONS

ServiceCallout

AssignMessage

RequestMessage

Message Validation

Step

TargetConfiguration

RouteRule

Connection

Path

When passing username and passwords.

When providing the ability to return different levels of detail in the response.

When requesting that an entire collection be deleted.

When filtering the response based upon a query

add headers

remove the payload

assign a value to a variable

all of the above

Modify the RouteRuies to be more specific.

Create a new proxy for this special condition.

Reorder the RouteRuies so that your condition is found

Add a new TargetServer to handle your specific condition

Use service callouts configuration for each target, and use a condition to decide which to invoke.

Use a Key-Value Map configuration to access SSL and URL information to invoke target systems

Use an AssignMessage policy to override default target URL and define 2-way SSL configuration at runtime

Create another target endpoint with SSL configured and define route rule to pick that depends on available variables.

Use XSLT to transform the XML payload and then use a XML to JSON policy

Use XML to JSON policy first to convert to JSON and then ExtractVariables with a JSONPath to extract the body from the converted SOAP envelope

Use ExtractVariables with an XPath first to extract the SOAP body and then use XML to JSON policy

Use an AssignMessage policy to convert the SOAP response to a JSON response, using XPath expressions to retrieve the data

Add smoke tests to your CI/CD process

Add code quality analysis into your CI/CD process.

Ask the developers to run unit tests prior to code check-in.

Ask the developers to run anti-virus against the code prior to check in.

Info

host

paths

license

swagger

basePath

produces

Authorization Code

Resource Owner Password Credentials

Refresh Token

Client Credentials