Abstract: An application programming interface (API) proxy intercepts API calls and responses for an application under test in a development environment, simulating (e.g., mocking) rate limiting and throttling behavior, which is otherwise challenging to test. The API proxy receives a API call and, based on a resource limiting parameter (e.g., rate-limiting or otherwise throttling), determines that the API call should be forwarded to the API endpoint. When the API proxy receives another API call from the application, destined for the same API endpoint, the API proxy determines to not forward the second API call, based on the resource limiting parameter (e.g., too soon after the first API call, or requests too much of a computational burden, such as exceeding a resource quota). The API proxy instead returns a throttling response, as would be expected from the API endpoint. The API proxy provides guidance messages for both outgoing calls and incoming responses.

Abstract: An application programming interface (API) proxy intercepts API calls and responses for an application under test in a development environment, simulating (e.g., mocking) rate limiting and throttling behavior, which is otherwise challenging to test. The API proxy receives a API call and, based on a resource limiting parameter (e.g., rate-limiting or otherwise throttling), determines that the API call should be forwarded to the API endpoint. When the API proxy receives another API call from the application, destined for the same API endpoint, the API proxy determines to not forward the second API call, based on the resource limiting parameter (e.g., too soon after the first API call, or requests too much of a computational burden, such as exceeding a resource quota). The API proxy instead returns a throttling response, as would be expected from the API endpoint. The API proxy provides guidance messages for both outgoing calls and incoming responses.