Endpoints returning extensive, unbounded result sets can significantly strain server resources, leading to performance degradation and potentially rendering the service unresponsive.
This case illustrates an endpoint that allows clients to request a large number of items without proper limitations. Implementing pagination or enforcing limitations on result set sizes is essential to prevent server strain, maintain optimal performance, and keep the service responsive.
get/performance/unbounded-result-set
Request
- Base URL: https://example.schemathesis.io
- URL: https://example.schemathesis.io/performance/unbounded-result-set
- Auth: api_key (a scheme the document does not define)
Query parameters
limitinteger required
The number of items to fetch. Must be greater than 0 and not exceed the maximum limit.
Response
Successfully fetched items.
object required
Changes
No recorded changes to this operation across all 1 revision of this API.