BigCommerce orders API: paginated retrieval with filtering (modified_date, order status)

Question

Podbox is building a connector using the BigCommerce orders API to synchronize orders from a BigCommerce e-store to cloud CRMs (like vTiger, Salesforce or ZohoCRM). As one of the developers, I found that there are unfortunately a couple of points that prevent the process from being efficient:

• it would be great to have a paginated retrieval, with page and limit parameters, as in the customers API. That would reduce the workload for both the BigCommerce server and the client server

• both customers and orders API calls return the date modified field and it would be great to use them as filters to retrieve the orders that were updated after a given date. With such criteria, the data returned by the API calls would be small, saving bandwidth and reducing workload for both BigCommerce and client servers too

• another optimization would be to use the status id criteria as a filter in order to retrieve only the uncomplete orders, but it seems that this criteria in only usable in the form of "status id equals [value]", I would like to use it in the form "status id differs from 7" (7 being the status id of a complete order) but it does not seem currently feasible to me

Would these feature requests be useful to other developers? Do some BigCommerce developers know whether these feature requests are on the road map? Or if I should propose them somewhere else?

Thanks anyway for your attention!

Answer 1

2 out of 3 request by you has already been implemented by BigCommerce.

• page and limit parameters

• You can pull modified orders by passing an 'If-Modified-Since' header. This will only return items that have been modified since the provided RFC-2822 date.

No idea about the status code issue, But i found this, I guess setting status_id filter as 0.

Hope this helps.