# Http\_poller handling paged responses

**URL:** <https://discuss.elastic.co/t/http-poller-handling-paged-responses/59095>\
**Category:** Logstash\
**Created:** [August 27, 2016, 2:49pm UTC](https://discuss.elastic.co/t/http-poller-handling-paged-responses/59095 "2016-08-27T14:49:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mkowalew3382](https://avatars.discourse-cdn.com/v4/letter/m/2bfe46/32.png) [@mkowalew3382](https://discuss.elastic.co/u/mkowalew3382)\
**Post date:** [August 27, 2016, 2:49pm UTC](https://discuss.elastic.co/t/http-poller-handling-paged-responses/59095/1 "2016-08-27T14:49:16Z")

</div>

We are polling data from a rest api and it pulls back a response in batches. Is there any way for the poller to go grab the next batch? As of right now it is only consuming the 1st 2000 items and never getting past it.

"@metadata": {  
"next\_batch": "[http://10.238.81.121:8080/rest/default/tamwe/v1/nfaflows?pagesize=2000&offset=2000](http://10.238.81.121:8080/rest/default/tamwe/v1/nfaflows?pagesize=2000&offset=2000)"

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 27, 2016, 11:36pm UTC](https://discuss.elastic.co/t/http-poller-handling-paged-responses/59095/2 "2016-08-27T23:36:14Z")

</div>

AFAIK there isn't, I've also looked.  
Please feel free to raise a feature request though 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 4:41am UTC](https://discuss.elastic.co/t/http-poller-handling-paged-responses/59095/3 "2017-07-06T04:41:18Z")

</div>

Closed on July 6, 2017, 4:41am UTC