Process	Description
1	The customer system makes a GET request to an InEight API. The InEight API successfully validates the request and returns a "202" response containing the "Location" element. The request is handed off to the InEight application business logic for processing.
2	The customer system polls the URL provided in the Location element. Because the JSON payload file is not yet ready, InEight returns a "202" response.
3	The customer system continues to poll the URL provided in the Location element. The JSON payload file is not available and InEight returns a "200" response with the file.
4	Because the JSON payload file contains the maximum number of records that can be returned by the API (500), the customer system determines that it should initiate another request to get more records.
5	The customer system makes a GET request to an InEight API and specifies that the first 500 records should be skipped ($skip=500). The InEight API successfully validates the request and returns a "202" response containing the "Location" element. The request is handed off to the InEight application business logic for processing.
6	The customer system polls the URL provided in the Location element. Because the JSON payload file is not yet ready, InEight returns a "202" response.
7	The customer system continues to poll the URL provided in the Location element. The JSON payload file is not available and InEight returns a "200" response with the file.
8	This time the JSON payload file contains 242 records, which is below the maximum that can be returned by the API, thus indicating there should be no more records and the customer system can stop making requests.