Hello Solvers,

This is an important note regarding the example API code that was posted on GitHub.

We have discovered a bug in the Python API example that affected the way that it retrieved pages of results in response to API queries (API paging is 1-based and not 0-based as had been stated). As a result, using the example code would result in receiving two copies of the first page (the first 10 records), and missing the second page of records. 

The documentation and code on the GitHub site has been updated to fix the bug. The official API documentation will be updated to clarify this point as well. If you are using the GitHub documentation or code posted prior to 10:30 AM Eastern time on 8 March, you should revisit the GitHub repository and take note of the update in the GfcApi._get_pages() function.

Specifically, the updated lines are:

page = 1

and 

while page <= maxPage:

If the code you are using to access the Cultivate API treats paging as 0-based, you should review and update your code, and re-query the API end-points you have already queried to ensure you have received all IFPs, human forecasts, and consensus forecasts.

You can see the updated documentation and code at: https://github.com/gfchallenge/gfc/blob/master/src/notebooks/GF%20Challenge%20API%20Example.ipynb