Cursor Pagination for Nested Object Key in API

Slack Knowledge Base Q&A Connector Development
, , , ,
21

"cursor":"{{ response.page_info.end_cursor if response and response.page_info.end_cursor else 'null' }}",
I’ve got this but I still get the same error :disappointed:

22

okay, try this:

  "adgroup_id": "{{ stream_partition.adgroup_id }}",
  "Content-Type": "application/json",
  "advertiser_id": "{{ stream_partition.advertiser_id }}",
  "pagination_parameters": {
    "cursor":"{{ next_page_token.next_page_token }}",
    "page_size": "1"
  }
}```
. . . I think where I was mixed up is that mine are date based so use `stream_interval`, but in your case `next_page_token` should contain the value of the matched cursor as long as it exists
23

if you run into problems with it not stopping at the end, you can use the Custom option and specify a more strict stop condition

24

oops, updated the above, it’s actually {{ next_page_token.next_page_token }}

25

You are a god amongst men :heart: That worked! Thank you so, so much!

26

It stopped on its own so no issue there

27

Genuinely mean it Justin, really appreciate you!!

28

Nice, glad that did it. I’ll try to drop in some docs fixes soon, because I don’t feel like this is clear at all in the docs (and should really show up in the info tooltip with a message like “This matched value is available in custom parameters or payloads using {{ next_page_token.next_page_token }}”)

29

Yes 100% agree - I had no idea that next_page_token was at thing, or even to look at this next_page_token.next_page_token notation!