The views items search resource pagination cursor format was changed

Starting from April 15, 2024, a breaking change has been implemented affecting the format of cursor values returned in the API response of views items search API.

Change

Before: Prior to this change, the format of the starting current_cursor value followed a specific pattern, exemplified by WyJuZXh0IiwgIjI4MzMzNDQyNCJd.

"meta": {
  "current_cursor": "WyJuZXh0IiwgIjI4MzMzNDQyNCJd",
  "next_items": "/api/views/10/items/?direction=next&ignored_item=1781&cursor=WyJuZXh0IiwgIjI4MzM0MjgxNiJd",
  "prev_items": null
}

After: The resource changed resulting in a different cursor format in response body WyJuZXh0IiwgIjE3MTMyOTMyMjIuNzAyIiwgIjI4MzMzNDQyNCJd.

"meta": {
  "current_cursor": "WyJuZXh0IiwgIjE2NjA0MzUyMDIiLCAiNjk4NjAxNCJd",
  "next_items": "/api/views/10/items/?direction=next&ignored_item=1781&cursor=WyJuZXh0IiwgIjE3MTMyODMyOTQuMTY2IiwgIjI4MzM0MjgxNiJd",
  "prev_items": null
}

Action required

Developers utilizing the affected endpoint (/api/views/0/items) and preserving the cursor on their end for polling functionality are advised to reset their existing cursor values with the ones returned from the API. Keeping on using the previous cursors might result in response errors.