My logic relies on this property but it's now missing. Is that a bug, api change, am I the only one missing this field? I'm wondering if it is safe to rely on this value.
The team confirmed that total should be used in place of total_counts and that the values should match. We will be updating the documentation accordingly.
If you're seeing discrepancies between the number of objects returned and the total value, could you share an example response via direct message which exhibits the issue?
Thanks for your reply. I do recieved the total field at the bottom of the response but it doesn't match the number of return objects like the total_count did.
Today we have changed our logic to count the numbers of objects in the response instead of relying on the total_count field.
The team confirmed that total should be used in place of total_counts and that the values should match. We will be updating the documentation accordingly.
If you're seeing discrepancies between the number of objects returned and the total value, could you share an example response via direct message which exhibits the issue?