REST API shows different structure for one endpoint
/tasks, /workflows and /workflow-instances shows a structure like this:
{
"total_pages": 1,
"page": 1,
"count": 26,
"data": [
{ ... }
]
}
But /workflow-instances/recurring-latest doesn't have that structure and just shows the data array:
[
{ ... }
]
Not sure if this is intentional or not. One way I've seen around returning pagination details in the body (and having to wrap the actual body) is to do it in the response headers.
@timwis /workflow-instances/recurring-latest does not paginate
Something that may make it more consistent is to return:
{
"count": 26,
"data": [
{ ... }
]
}
Keeps a more simpler structure without making it seem paginated
Yep, or putting the count/page/total values in response headers and just keeping the body as the data.