Polling repeatedly sends requests to check the status of an asynchronous operation. It avoids keeping a connection open for work that may last minutes or hours, reducing timeout and scalability risks. section 14.7 section 14.7.1
Monitoring a stress test
A dashboard starts a stock-market simulation with POST /simulations. The API returns 202 Accepted, current status, and Location: /simulations/12345. The dashboard then calls GET /simulations/12345 until the status changes from IN_PROGRESS to DONE. section 14.7.1
Make polling more efficient by:
- Returning progressPercentage, progressPercentagePerMinute, or estimatedEnd so consumers can adjust request frequency. section 14.7.1
- Returning Retry-After with an estimated completion time when another wait is appropriate. section 14.7.1
- Considering callbacks or webhooks as alternatives, while retaining retrieval for consumers that cannot implement them. section 14.7 section 14.9








