Pagination
Where one page of a search stands.
Fields #
| Field | Type | Notes |
|---|---|---|
page | integer | 1-based, and equal to the entry's own page. |
returned | integer | Rows on THIS page, which is what you were billed for. |
has_more | boolean | False on the last page. Derived from the page coming back short or empty - never from total. On a chunked search it is about THIS chunk: the entry after a false is the next chunk first page, which is what chunk.index is for, and the batch status is what says the target is done. |
total | integer | LinkedIn's own match count, and advisory only. On a broad search it reports the whole universe - tens of millions - while the search itself stops serving at the ceiling. Never use it to decide when to stop. |
display_total | string | The same figure as LinkedIn renders it: "35", or "26M+". A string for that reason. |
Absent is not null: a field we did not get is omitted rather than sent as an empty string, so you can tell "LinkedIn does not have this" from "this person left it blank".
Sample #
{ "page": 3, "returned": 100, "has_more": true, "total": 4182, "display_total": "4,182" }