Discussions

Hi everyone,
I’m currently working on an integration (slope) using the Zuper API and wanted to start a discussion around best practices for structuring efficient API calls, especially as projects grow in complexity and scale.
I’m fetching and syncing data (such as jobs, customers, and related entities) between Zuper and an external system. While the API works well, I want to make sure I’m designing my calls in a way that is
Performant
Scalable
Easy to maintain
Friendly to rate limits
What’s the best way to use filters and pagination to avoid over-fetching data?
Any tips for efficiently handling large datasets (e.g., jobs or customers)?
Thanks in advance!