# Getting around API call record limits

**URL:** <https://connective.celigo.com/t/getting-around-api-call-record-limits/94>\
**Category:** Integrator.io\
**Tags:** http, export, javascript, flow-builder\
**Created:** [June 27, 2024, 4:49pm UTC](https://connective.celigo.com/t/getting-around-api-call-record-limits/94 "2024-06-27T16:49:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cascadeservicecascad](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@cascadeservicecascad](https://connective.celigo.com/u/cascadeservicecascad)\
**Post date:** [June 27, 2024, 4:49pm UTC](https://connective.celigo.com/t/getting-around-api-call-record-limits/94/1 "2024-06-27T16:49:27Z")

</div>

I have built a custom flow using an HTTP connector, and the API I am using has a 1000 record limit which you can set in the request body. Is there a way in Celigo without using Javascript to either a) have the export step repeat itself but with a different http request body within a flow or b) have multiple export steps that use the same call but different request body that then append together before the other steps in a flow?  
The only way I could think to do so would be to create a copy of the flow within the integration for each 1000 records, so I would have multiple flows that ran in sequence but that seemed like it probably wouldn't be ideal.

---

<div class="post-metadata">

**Author:** ![youssefzouhairi](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/youssefzouhairi/32/7087_2.png) [@youssefzouhairi](https://connective.celigo.com/u/youssefzouhairi)\
**Post date:** [June 27, 2024, 5:20pm UTC](https://connective.celigo.com/t/getting-around-api-call-record-limits/94/2 "2024-06-27T17:20:53Z")

</div>

Hi @cascadeservicecascad,   
Not sure about the details of your use case or your API (maybe you can post here the doc of the API if that's public), but I think you can definitely in the same flow, use multiple exports (by adding sources). The issue with that, is that it will be a static export.

---

<div class="post-metadata">

**Author:** ![cascadeservicecascad](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@cascadeservicecascad](https://connective.celigo.com/u/cascadeservicecascad)\
**Post date:** [June 27, 2024, 6:19pm UTC](https://connective.celigo.com/t/getting-around-api-call-record-limits/94/3 "2024-06-27T18:19:02Z")

</div>

@youssefzouhairi Unfortunately I don't believe it is public. I figured out how to add multiple sources but wasn't sure how to append them together before the lookup/import steps. Is there an online learning or document that goes over that? I looked but it's possible I didn't have the search terms right.  
I'm fine with it being static, and just adding a new source each time we add another 1000 records as it doesn't get posted to frequently enough to be an issue.

---

<div class="post-metadata">

**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\
**Post date:** [June 27, 2024, 11:43pm UTC](https://connective.celigo.com/t/getting-around-api-call-record-limits/94/4 "2024-06-27T23:43:31Z")

</div>

@cascadeservicecascad you can probably set up a paging mechanism. Maybe use the custom request body option: [https://docs.celigo.com/hc/en-us/articles/360059620151-API-pagination](https://docs.celigo.com/hc/en-us/articles/360059620151-API-pagination)