question

richa avatar image
richa asked hilarybrown answered

Fetching all orders using REST API instead of orders as per provided timestamp

Orders REST API
3 comments
10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

cherry avatar image cherry commented ·

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.

Justin Tucker Contract

0 Likes 0 ·
contactpackage avatar image contactpackage cherry commented ·

The issue might be due to how the API handles timestamp filtering or how the query parameters are being passed. Make sure you're using the correct timestamp format and that your API endpoint supports precise time-based filtering as you expect.


Double-check the API documentation, verify the timestamp format, and ensure you're passing the timestamp parameters correctly in your request to get the exact orders within the specified time range.

_________________________________________

moto x3m

0 Likes 0 ·
pammelala avatar image pammelala commented ·

If you are looking for a fun game that doesn’t require too much thinking, then Block Blast is definitely for you!

0 Likes 0 ·
David Marginian avatar image
David Marginian Deactivated answered David Marginian Deactivated commented

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.

2 comments
10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

richa avatar image richa commented ·

My code is as follows :

const options = {

method: 'GET',

url: ' 0 Likes 0 ·

David Marginian avatar image David Marginian ♦♦ richa commented ·

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

0 Likes 0 ·
cherry avatar image
cherry answered

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

10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

hilarybrown avatar image
hilarybrown answered

It sounds like you're encountering an issue with your REST API query not filtering orders by the provided timestamp. Ensure your API endpoint is correctly implemented to handle query parameters. You might also want to check if your database query is accurately filtering results. Meanwhile, if you need a break from debugging, why not play Papa's Pizzeria for some fun? It’s a great way to unwind!

10 |2000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Welcome to the
Clover Developer Community