We are having a web/integrator company assist us with a BigCommerce to NetSuite integration.
Below is their input from their experience so far in creating the integration and testing. We would like to understand if 'Bulk Queries' and Webhooks' may be part of the future landscape for NetSuite?
"Over the past several months, we have been running into API call limitations. What's going on is related to the lack of not having a Bulk Query capability (for reference, check out BigCommerce and their Bulk Query capability). So even though the NetSuite API has specific endpoints (that would be appropriate to use in certain situations), when we need massive amounts of data to run through those endpoints, combined with other calls to get additional information (for say products / inventory, customers, sales orders, order items, payments, etc.), the calls start hitting limits / timing out. With these limits (understandably) we are basically locked out from continued testing for a period of time (call limit duration), which then also delays further API development.
How can Bulk queries help? Bulk queries give the API developer the ability to query larger data sets (essentially a SQL query), being only 1 call (or multiple if the results are paged), being able to query exactly what's needed (with joins) and have the ability to get it in one set (or paged result sets as mentioned above, which is better than the massive transactional calls being made currently; essentially we'd like to favor quality calls over quantity of calls). This allows us to not have to make extra API calls (to "fill in the gaps" between what calls return, as they are transactional) and allows us to actually request less data in the long run (and less frequently).
Another feature that would be super helpful (that most modern APIs make available) is what is called Webhooks (for reference, check out BigCommerce and their Webhooks capability). Webhooks allow an API integration to call data only when data has changed via system events, such as when a customer is updated or when an order is created, etc. (instead of making periodic scheduled API calls to see if anything has changed). This feature also (in the end) would help the API system at NetSuite to actually request less data (only when needed).
Both features above (Bulk Queries and Webhooks) would be a win-win for all parties (the Customer, in this case Strider; the API provider, in this case NetSuite; and the API developer, in this case Projex)."