Why Search endpoints is limiting data to 250?

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Suppose if I want to fetch all terminated users via search, it only shows 250 records. I need to get all records calling API in my program to get information of each user.

The documentation clearly states that for search API, the limit is 10000.

2

Did you try pagination?

3

You need to use offset to fetch subsequent records. After 10000 records you have to use searchAfter in the request body and get rid of offset in query

1 Like
4

@iamnithesh , I know way to fetch all data with offset and limit adding to url. But just wondering if all the records(in the limit of 10000) can be fetched or not without using offset and limit.

It seems I should use offset and limit in url as parameters to fetch those first 10000 records as well. Otherwise, only first 250 records are showing.

5

Could you provide an example of the search you are making, and the paramerters you are setting for it? Can you try it with specifying the limit as 10000 and the offset as 0? If you only get 250 with those set, can you set the offset to 1 and check to see if you get the same results?

I do agree that the documentation states that you should be able to set the value up to 10,000. I wonder if the default is 250 (or if the page size changed to 250) and the documentation does not reflect it yet. I also found the standard variables state that it should be 10,000 also: Standard Collection Parameters | SailPoint Developer Community

This will likely need the @developer_advocates to weigh in on this.

1 Like
6

Our search API is now returning 250 as the default. To get to the 10,000 limit, you must specify the limit parameter. We will be updating the documentation accordingly.

/v2024/search?limit=10000

4 Likes
7

This is awesome!! Now we can simplify our script to make Search API calls. However, I would be cautious about the response json body size and probably use queryResultFilter to limit the returned content length

8

Will the SearchAfter still need to be used to get back more than 10,000 results, or can the offset be used to get the next 10k?

/v2024/search?limit=10000&offset=10000

Great suggestion on the queryResultsFilter and monitoring the json body size.

9

Yes, the search after still needs to be used.

1 Like
10

Thank you all for the resolution to the issue.

11

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.