I’m wondering if we can increase the ‘take’ limit on the ‘get-type-curve-daily-fits’ endpoint to 18,500 (~50 years). I accomplished the same by just looping over the query in 200 day blocks but would like to call it just once.
Keeping HTTP API responses under 1 MB improves responsiveness and reliability, so it’s not recommended to return 18,500 records (6+ MB) in one call.
Responsiveness
Smaller payloads load faster, reducing lag for users and integrations. This is especially important when chaining multiple API calls.
Reliability
Large responses are more prone to timeouts, dropped connections, or issues from intermediary systems (e.g., CDNs, gateways) that cap response sizes or timeouts.
Consistency Across Clients
Many HTTP clients have implicit size or memory limits. Keeping responses light ensures consistent behavior across tools.
That makes sense. Could there be a work around in the future w/ pagination of the larger datasets for export? In the meantime, I chose to utilize an async function to query all the data a little faster.
I had one of the Developers look into it further. We’re going to try bumping the Take to 2500; hopefully, it will be out in the next release.
1 Like