Description
The Paging response model does not include a next_page_token field. LinkedIn's REST API uses cursor-based pagination for several endpoints (e.g., ad analytics finder), returning a next_page_token in the paging metadata. Since the model lacks this field, users cannot implement cursor-based pagination without manually parsing the raw response.
Impact
Cursor-based pagination is silently broken — the SDK strips out the token that the API returns, forcing users to drop down to raw HTTP to paginate.
Suggested fix
Add next_page_token: Optional[str] to the Paging model. See PR #74.
Description
The
Pagingresponse model does not include anext_page_tokenfield. LinkedIn's REST API uses cursor-based pagination for several endpoints (e.g., ad analytics finder), returning anext_page_tokenin the paging metadata. Since the model lacks this field, users cannot implement cursor-based pagination without manually parsing the raw response.Impact
Cursor-based pagination is silently broken — the SDK strips out the token that the API returns, forcing users to drop down to raw HTTP to paginate.
Suggested fix
Add
next_page_token: Optional[str]to thePagingmodel. See PR #74.