Is there a fixed result limit via REST

Mchoeti · 2022-01-18T10:15:27+00:00

There was an error rendering this rich post.

Hi all!

We habe updated our servers to CS 20.4 and today i experienced a funny situation. As always we are dooing some REST calls to filter the results according to our required parameters. In the past we had set the limit to 300 and now it seems like the range_max is about 100

Here is the call. You can filter until the value of 100 which means 99 works, 111 not

GET: https://your.server/api/v2/nodes/18166308/nodes/?fields=properties{create_date,id,name}&limit=99&sort=desc_create_date

But when i try to use more results than 100 . In this example 111 it seems like that the call only allows 100.

GET : https://your.server/api/v2/nodes/18166308/nodes/?fields=properties{create_date,id,name}&limit=111&sort=desc_create_date

As you can see the response from the body is:

''' 
    "collection": {
        "paging": {
            "limit": 100,
            "links": {
                "data": {
                    "next": {
                        "body": "",
                        "content_type": "",
                        "href": "/api/v2/nodes/18166308/nodes/?fields=amcsproxy&fields=properties{create_date,id,name}&limit=100&sort=desc_create_date&page=2",
                        "method": "GET",
                        "name": "Next"
                    }
                }
            },
            "page": 1,
            "page_total": 450,
            "range_max": 100,
            "range_min": 1,
            "total_count": 44918
        },

'''

Any ideas how i can solve this ?

Cheers Christian

Find more posts tagged with

API

Content Services

Comments

Greg Griffiths

Looking at the supporting info for the method call (https://developer.opentext.com/resources/documentation/14ba85a7-4693-48d3-8c93-9214c663edd2/c9a6ccae2d680fd39218145f567715b5/page/3.2) the parameter limits the number of rows returned in the request.

Is it your REST code that is setting the value or OTs ?

Mchoeti

@Greg Griffiths

Well normally when i try to use it with the browser there are more than 100 results. As you can see in my REST call example. When i use 99 as the limit value it brings me back 99 values. But when i go gigher as example 111 only 100 results will returned.

I do this

https://........../?fields=properties{create_date,id,name}&limit=111&sort=desc_create_date

and this is that i got in the body.

"href": "/......... amcsproxy&fields=properties{create_date,id,name}&limit=100&sort=desc_create_date&page=2",

For me it looks like that there is a fixed limit with 100. Could that be ?

cheers Ch

Greg Griffiths

yep, limited to 100 per page now for performance, so you would need to use the pagination functionality - https://knowledge.opentext.com/knowledge/llisapi.dll/kcs/kbarticle/view/KB19921351