GetFills endpoint inconsistency

Hi,

We’ve noticed that when reading fills, responses can be incomplete (e.g. fills were executed but aren’t returned in the response). To accommodate this, we’ve created separate processes which go back in time and ping GetFills again to see if there are missing fills that weren’t returned by earlier calls.

It would seem that a better solution would be to have stronger guarantees of consistency from the Coinbase API. Is this something the team is aware of/working on? Benefits being an easier-to-use API and fewer calls from clients who aren’t sure if responses are complete.

Thanks–Z

1 Like

Hello @genesisguy . Welcome to the forum! Thank you for taking an interest in trying out Coinbase APIs. For the details regarding your concern, we will check on this for you with our team. We will get back to you once we have more information. Keep in touch!

Hi @genesisguy, thank you for your patience. For us to be able to help you further, we’d like to ask how you are sending your GET request.

  • Are you querying by order_id or product_id?
  • We’d also like to know if you are setting a limit parameter for the number of results you want to be returned.
  • Lastly, are you using the before or after parameters to paginate the results?

Once you provide us with more information, we’d help you as soon as possible.

2 Likes

Hi yes, here are some answers:

  • Are you querying by order_id or product_id?
    Product id

  • We’d also like to know if you are setting a limit parameter for the number of results you want to be returned.
    Limit is 100, and we’re calling infrequently so as to not get rate limited.

  • Lastly, are you using the before or after parameters to paginate the results?
    Yes, we always provide before/after cursors. Sometimes, the upper time bound is the current time, and other times we search in the past to see if there were any fills that previous calls did not include.