Our API calls are based on the last modified date of a record. The API call that happens once a day will look at the last modified date in the table and request all records from that point on. This is the same process that we have set up for all of the Reapit API calls and most seem to work fine.
When calling the ID checks call, it seems that the REST API service from REAPit’s end is not returning data based on the modified date provided.
The call comes back as successful, however, always starts again from 2016 even though a date in 2021 was provided. We have tested this also within Postman and getting the same results of the data being returned not meeting the criteria for the modified date (despite being available in the documentation).
If you would like to try this yourself, the call is as follows:
Logged originally as part of https://github.com/reapit/foundations/issues/5165
Our API calls are based on the last modified date of a record. The API call that happens once a day will look at the last modified date in the table and request all records from that point on. This is the same process that we have set up for all of the Reapit API calls and most seem to work fine.
When calling the ID checks call, it seems that the REST API service from REAPit’s end is not returning data based on the modified date provided.
The call comes back as successful, however, always starts again from 2016 even though a date in 2021 was provided. We have tested this also within Postman and getting the same results of the data being returned not meeting the criteria for the modified date (despite being available in the documentation).
If you would like to try this yourself, the call is as follows:
https://platform.reapit.cloud/identityChecks/?PageSize=100&modifiedFrom=2021-09-14&sortBy=modified
Specification