When querying the API we'll need to implement pagination by passing specific LIMIT / OFFSET parameters to the query.
We want to be able to gauge the full data size in the response, even with these parameters added.
Currently suggested workaround are:
  1. creating a separate SELECT count(*) FROM query
  2. create a conditional loop
These are fine interim solution, but could get expensive and we'd like to be cost efficient as we scale. Thus, we'd love to have pagination natively supported via the API.