Ensure the API query parameters for the timestamp are correct and match the required format. If the issue persists, test with tools like Postman to verify if the problem is with the API or your Node.js code. As a workaround, consider client-side filtering to narrow down results.
We can't tell you what the problem is in your code if you haven't included any of your code to look at. I suggest that you take a look at your code in more detail.
Why aren't you passing the filters as part of the query string (qs)? I am not sure what library you are using to make the request, but when you pass special characters (>=) in a URL they need to be encoded correctly. I assume passing them in the qs will do that, otherwise you need to encode the querystring in the url you are passing. Also, you shouldn't be passing the access token in the query string, you should be using a header - https://docs.clover.com/docs/using-api-tokens
The issue could stem from an incorrect timestamp format, misconfigured API parameters, server-side bugs, caching, or time zone mismatches. Double-check the API documentation, ensure you're using the correct query parameters, and log your requests to verify the timestamps. If the issue persists, contact the API provider for support. Katt Williams Net Worth
3 People are following this question.