Skip to content

Paging model missing next_page_token field for cursor-based pagination #78

Description

@ZLeventer

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions