# Type Curve Exports via API

**URL:** <https://forum.api.combocurve.com/t/type-curve-exports-via-api/430>\
**Category:** Feedback\
**Tags:** feature-request, python\
**Created:** [July 29, 2025, 8:50pm UTC](https://forum.api.combocurve.com/t/type-curve-exports-via-api/430 "2025-07-29T20:50:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kmckee](https://avatars.discourse-cdn.com/v4/letter/k/6de8d8/32.png) [@kmckee](https://forum.api.combocurve.com/u/kmckee)\
**Post date:** [July 29, 2025, 8:50pm UTC](https://forum.api.combocurve.com/t/type-curve-exports-via-api/430/1 "2025-07-29T20:50:28Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Danny\_Cooney](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.api.combocurve.com/danny_cooney/32/256_2.png) [@Danny\_Cooney](https://forum.api.combocurve.com/u/Danny_Cooney)\
**Post date:** [July 30, 2025, 1:25pm UTC](https://forum.api.combocurve.com/t/type-curve-exports-via-api/430/2 "2025-07-30T13:25:45Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![kmckee](https://avatars.discourse-cdn.com/v4/letter/k/6de8d8/32.png) [@kmckee](https://forum.api.combocurve.com/u/kmckee)\
**Post date:** [July 30, 2025, 4:36pm UTC](https://forum.api.combocurve.com/t/type-curve-exports-via-api/430/3 "2025-07-30T16:36:55Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Danny\_Cooney](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.api.combocurve.com/danny_cooney/32/256_2.png) [@Danny\_Cooney](https://forum.api.combocurve.com/u/Danny_Cooney)\
**Post date:** [July 30, 2025, 7:17pm UTC](https://forum.api.combocurve.com/t/type-curve-exports-via-api/430/4 "2025-07-30T19:17:55Z")

</div>

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.