The `$top` system query option states the maximum number of rows. It is the way to look at a table without downloading it. ## Request ```text GET .../odata4/ExactOnlineREST.Financial.GLAccountsBulk@eol?$top=10 ``` ## Which Ten Rows Without an order the ten rows are whichever ten the platform answers first, which is not a promise and may differ between two identical requests. An order makes the choice explicit: ```text GET .../odata4/ExactOnlineREST.Financial.GLAccountsBulk@eol?$orderby=Code desc&$top=10 ``` ## No Second Page `$top` is a limit and not the first page of a walk. The protocol offers no paging: `$skip` with a value other than `0` and `$skipToken` are both refused, and the answer carries no `@odata.nextLink`. A request either retrieves what it asks for, or it asks for less. Where a table is too large to retrieve at once, the way forward is a narrower question rather than a smaller page: fewer columns with [[Select Columns]], fewer rows with [[Filter Rows]], or totals instead of rows with [[Group and Aggregate Rows]].