Pagination issue with Search/EquitySearch
When I make the following request:
POST /RestApi/v1/Search/EquitySearch HTTP/1.1
Host: hosted.datascopeapi.reuters.com
Authorization: Token <token>
Content-Type: application/json
Cache-Control: no-cache
Postman-Token: f0cacf9b-0998-4e87-1385-e984cc32b255
{
"SearchRequest": {
"ExchangeCodes": ["NEO"]
}
}
I get back the seemingly appropriate response with a list of 250 objects under the 'value' key. There is also the @odata.nextlink": "https://hosted.datascopeapi.reuters.com/RestApi/v1/Search/EquitySearch?$skiptoken='MjUw'
However, when I follow the nextlink with the following request:
POST /RestApi/v1/Search/EquitySearch?$skiptoken='MjUw' HTTP/1.1
Host: hosted.datascopeapi.reuters.com
Authorization: Token <token>
Content-Type: application/json
Cache-Control: no-cache
Postman-Token: f8126ddd-e95c-891d-3fe6-8ecae3d5b097
{
"SearchRequest": {
"ExchangeCodes": ["NEO"]
}
}
Instead of getting the next batch of items (presumably another 250, the same as the default for the first) I get 500, including the first 250 from the previous request and response.
Following the next nextlink yields 750, including many, but not all, of the items from the previous two requests.
As I follow the nextlinks the response size increases, and eventually reaches a steady state where new nextlinks are returned but the returned values are the same every time.
This behaviour occurs both in Postman and in custom Python code using the requests library. Manual pagination using the $top and $skip parameters yields similar results. Through experience, this particular query has ~5600 unique objects in its result set, and if I request a maxpagesize of 6000 I get them all in one request.
I have used the odata.nextlink pagination method successfully with the VenueByDay endpoints for retrieving large numbers of venue files, so I don't believe my implementation of the handling of odata.nextlink is at fault. Is it possible that there is an ordering issue server-side?
Answers
-
Hi @acampbell
I am able to replicate the issue too. The response returned from next link should be next 250 rows only. It seems like the issue is in server side. Please contact DSS support team via the Raise A
Case,selecting product "Reuters DataScope Select".0 -
Pagination is not fully implemented for searches. This thread and this thread give a few details.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 688 Datastream
- 1.4K DSS
- 624 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 557 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 276 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 692 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 105 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 10 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛