Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The actual hit count in each of the three categories and the current thresholds will be included in the error or warning returned to the consumer as part of the response when rate limiting is triggered.

The weight of every service (number of hits consumed by each invocation) is documented on the documentation page for that service.

PWS Service Responses


For the responses to PWS Services, when a Rate Limit Violation is encountered, the PWS Error Code that is raised is “RequestExceededRateLimit” with the Error Number of 10016.  This is true whether or not the violation triggers a warning or an error in the response.

...

For a list of PWS Web Services and their associated weight classes/hits, please view: Rate Limiting - PWS Web Service Weights


Legacy Service Responses


For the responses to Legacy Services, when a Rate Limit Violation is encountered, the Error Code that is raised is similarly “RequestExceededRateLimit”.  This is true whether or not the violation triggers a warning or an error in the response.

...

For a list of Legacy Web Services and their associated weight classes/hits, please view: Rate Limiting - Legacy Web Service Weights


Currently, all restful service invocations piggy-back on the PwsGetReportOutput service which is midweight and counts for two hits.

...