# Pagination for Okendo.io API

**URL:** <https://community.parabola.io/t/pagination-for-okendo-io-api/2642>\
**Category:** Ask a question\
**Tags:** Using-APIs\
**Created:** [January 25, 2023, 3:04am UTC](https://community.parabola.io/t/pagination-for-okendo-io-api/2642 "2023-01-25T03:04:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Johnathan\_Ruggiero](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/johnathan_ruggiero/32/2015_2.png) [@Johnathan\_Ruggiero](https://community.parabola.io/u/Johnathan_Ruggiero)\
**Post date:** [January 25, 2023, 3:04am UTC](https://community.parabola.io/t/pagination-for-okendo-io-api/2642/1 "2023-01-25T03:04:46Z")

</div>

Hello! I’m trying to download our Okendo reviews via API and I’m running into some pagination issues. I can’t get it to show more than one page of records.

I believe I’ve incorrectly set up the pagination settings. Please see attached for what I’m using. Thank you!

John

 ![Screen Shot 2023-01-24 at 8.02.56 PM](https://us1.discourse-cdn.com/flex020/uploads/parabola/original/2X/4/427278372663a744d047f9fefa91acfd2a44ab07.png)  
 ![Screen Shot 2023-01-24 at 8.02.42 PM](https://us1.discourse-cdn.com/flex020/uploads/parabola/original/2X/5/5faa4f837253546406d651d5d7d98938e42ea136.jpeg)

---

<div class="post-metadata">

**Author:** ![Ayana\_Usui](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/ayana_usui/32/1985_2.png) [@Ayana\_Usui](https://community.parabola.io/u/Ayana_Usui)\
**Post date:** [January 25, 2023, 11:57pm UTC](https://community.parabola.io/t/pagination-for-okendo-io-api/2642/2 "2023-01-25T23:57:14Z")

</div>

Hey @Johnathan_Ruggiero

It looks like this is a partial URL which Parabola can’t read today. Unfortunately we won’t be able to set up the pagination for this endpoint using our API step!

Ayana

---

<div class="post-metadata">

**Author:** ![Johnathan\_Ruggiero](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/johnathan_ruggiero/32/2015_2.png) [@Johnathan\_Ruggiero](https://community.parabola.io/u/Johnathan_Ruggiero)\
**Post date:** [January 26, 2023, 1:06am UTC](https://community.parabola.io/t/pagination-for-okendo-io-api/2642/3 "2023-01-26T01:06:55Z")

</div>

I thought that was what the “cursor path in response” section was for? Domain there and then it would append the rest of the path from the nextUrl?

---

<div class="post-metadata">

**Author:** ![brian](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/brian/32/11_2.png) [@brian](https://community.parabola.io/u/brian)\
**Post date:** [January 27, 2023, 5:31pm UTC](https://community.parabola.io/t/pagination-for-okendo-io-api/2642/4 "2023-01-27T17:31:07Z")

</div>

Hey @Johnathan_Ruggiero,

I can hop in here and clarify!

`Cursor path in response` is the path to get to the field in the response from the API that contain the cursor you want to use - for your API, you would use `nextUrl` in that field.

If the cursor could be sent back to the API in a query parameter, such as `my.api.com/orders?nextPage=abdxyz1234`, then the `Cursor key` field would need to be set to `nextPage`, as that is the name of the (example) parameter to use.

If the value of `nextURL` was a full URL, the construction of a query parameter using the `Cursor key` would be skipped, and the step would fetch the next page using the whole URL.

At the moment, we do not have a way to merge in the base URL to a partial cursor URL like this unfortunately!