I managed to resolve it, apparently it wasn't caching, but rather some change in the API token, I don't know if it was my client who made the change or someone on his team, but apparently it was because of this.
1 Like