For a card to be eligible to be refreshed, it must comply with the following conditions:
Schedule refresh must be set as true for the card.
The card must have had a successful connection in the last 10 days (GetDetailsCompleted with no authentication related error - this includes both cached and live calls).
The card should not have had any errors during Authorization or the error should have been: RETRY_LATER, AGGREGATION_ERROR, SESSION_EXPIRED, DISABLED_INSTITUTION, UNAUTHORIZED, SESSION_NONEXISTENT, BANK_MAINTENENACE_RETRY_LATER
/GetNightlyRefreshStatus: is the endpoint that returns a list with all the LoginIds that are set to nightly refresh ("IsScheduledRefresh": true), however are no longer refreshing due to errors. Its JSON response will also clarify what was the encountered error on the refresh attempt.
/Authorize: when running the batched cached calls, this endpoint will also return the error message from the previous refresh attempt. In case it doesn’t return any errors, i.e. 200, please make sure you check the date of the latest refresh, as in the snapshot below:
In case this date is too long ago for your use case, please perform a manual refresh. This can be done just by changing the body parameters in /Authorize, as in the example below, and subsequently calling our aggregation endpoints with the provided RequestId.
For additional information, please do not hesitate to reach out to our support team at: