Hey community,
I'm experiencing an issue with the Miro API when using the groups endpoint:
https://api.miro.com/v2/boards/{board_id}/groups?limit=50
The pagination doesn't seem to work as expected. Instead of navigating to the next page of groups, it redirects me to pagination for items.
Is this the expected behavior, or could it be a bug? Any insights would be appreciated!
Thanks in advance!
Payload:
Best answer by vkoko
Hello
Yes, the API returned more than 50 results.
When I manually added the cursor as a query parameter to the get groups endpoint, it worked correctly.
Previously, my app was automatically handling pagination by following the link provided in the payload. However, I encountered some unexpected results, which is why I raised this issue.
To resolve it, I implemented a workaround: extracting the cursor from the payload and appending it to the link manually.
It would be helpful if, in the future, the Miro API consistently included the get groups endpoint with the cursor already appended in the payload, similar to how pagination works with other endpoints.
Thanks
Vas
+1Hey
I am assuming that the API returned more than 50 results, is that right?
What is the response like if you use the cursor parameter which you got `MzQ10Dc….` into the next API call, does it return the next set of results? Could you please also share what that response looks like?
If you could share the limit, and size parameters from both responses it will help us debug.
Hello
Yes, the API returned more than 50 results.
When I manually added the cursor as a query parameter to the get groups endpoint, it worked correctly.
Previously, my app was automatically handling pagination by following the link provided in the payload. However, I encountered some unexpected results, which is why I raised this issue.
To resolve it, I implemented a workaround: extracting the cursor from the payload and appending it to the link manually.
It would be helpful if, in the future, the Miro API consistently included the get groups endpoint with the cursor already appended in the payload, similar to how pagination works with other endpoints.
Thanks
Vas
+1Hi
I’m glad you found a workaround. I will add this feedback for our teams to prioritize what to improve next in our developer platform. This is super helpful for us so thank you for this thoughtful feedback.
Please don’t hesitate to reach out if you have further questions, we really appreciate all of your contributions for our community!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
