Pagination
27 distinct extensions were invented to do this job. Each one is a provider deciding OpenAPI would not carry something and building their own way through. Where a job has many names and few uses each, nobody won — the problem was solved privately, over and over.
27 extensions
10441 occurrences
9 vendor-named
The extensions
| Extension | What it appears to do | Uses | Providers |
|---|---|---|---|
|
x-ms-pageable
vendor |
`x-ms-pageable` appears on operations. Its value is a structured object. Used by 10 providers across 547 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooling ra | 9578 | 10 |
|
x-speakeasy-pagination
vendor |
`x-speakeasy-pagination` appears on operations. Its value is a structured object. Used by 7 providers across 9 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its meaning is defined by | 107 | 7 |
| x-paginated-items | `x-paginated-items` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 17 OpenAPI documents. Consistent with pagination — this is inferred from whe | 96 | 1 |
| x-paging-default-max-items | `x-paging-default-max-items` appears on operations. Its value is an integer. Used by a single provider across 20 OpenAPI documents. Observed values include `100`, `20`, `10`, `50`. Consistent with pag | 90 | 1 |
| x-paging-input-token | `x-paging-input-token` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 20 OpenAPI documents. Consistent with pagination — this is inferred from | 90 | 1 |
| x-paging-output-token | `x-paging-output-token` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 20 OpenAPI documents. Consistent with pagination — this is inferred from | 90 | 1 |
| x-paging-page-size | `x-paging-page-size` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 20 OpenAPI documents. Consistent with pagination — this is inferred from wh | 90 | 1 |
| x-paging-result | `x-paging-result` appears on schema objects and properties. Its value is a boolean flag. Used by a single provider across 20 OpenAPI documents. Consistent with pagination — this is inferred from where | 90 | 1 |
| x-pagination | `x-pagination` appears on operations. Its value is a structured object. Used by 3 providers across 5 OpenAPI documents. Consistent with pagination — this is inferred from where the key appears and wha | 43 | 3 |
| x-tale-pagination | `x-tale-pagination` appears on response objects. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `keyset`, `none`, `offset`. Consistent with paginat | 33 | 1 |
|
x-equinix-metal-paginated-property
vendor |
`x-equinix-metal-paginated-property` appears on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. It sits in the `x-equinix-` namespace, so its meaning is defined by e | 28 | 2 |
| x-page-size | `x-page-size` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with pagination — this is inferred from where the key appears | 26 | 1 |
| x-polygon-paginate | `x-polygon-paginate` appears on operations. Its value is a structured object. Used by a single provider across 18 OpenAPI documents. Consistent with pagination — this is inferred from where the key ap | 19 | 1 |
| x-next-cursor | `x-next-cursor` appears on header objects. Its value is a structured object. Used by 2 providers across 3 OpenAPI documents. Consistent with pagination — this is inferred from where the key appears an | 17 | 2 |
|
x-fern-pagination
vendor |
`x-fern-pagination` appears on operations. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-fern-` namespace, so its meaning is defined by fern | 9 | 1 |
| x-supra-cursor | `x-supra-cursor` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with pagination — this is inferred from where the key appe | 7 | 1 |
|
x-sendcloud-paginated
vendor |
`x-sendcloud-paginated` appears on operations. Its value is a boolean flag. Used by a single provider across 3 OpenAPI documents. It sits in the `x-sendcloud-` namespace, so its meaning is defined by | 5 | 1 |
|
x-sendcloud-paginated-discriminator
vendor |
`x-sendcloud-paginated-discriminator` appears on operations. Its value is a string. Used by a single provider across 3 OpenAPI documents. It sits in the `x-sendcloud-` namespace, so its meaning is def | 5 | 1 |
|
x-stainless-pagination-property
vendor |
`x-stainless-pagination-property` appears on schema objects and properties and on parameter objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in t | 3 | 1 |
|
x-ms-blob-append-offset
vendor |
`x-ms-blob-append-offset` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. It sits in the `x-ms-` namespace, so its meaning is defined | 2 | 1 |
| x-paginates | `x-paginates` appears on operations. Its value is a boolean flag. Used by a single provider across 2 OpenAPI documents. Consistent with pagination — this is inferred from where the key appears and wha | 2 | 1 |
| x-pagination-limit | `x-pagination-limit` appears on header objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with pagination — this is inferred from where the key | 2 | 1 |
| x-pagination-page | `x-pagination-page` appears on header objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with pagination — this is inferred from where the key | 2 | 1 |
| x-pagination-total | `x-pagination-total` appears on header objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with pagination — this is inferred from where the key | 2 | 1 |
| x-pagination-total-pages | `x-pagination-total-pages` appears on header objects. Its value is a structured object. Used by a single provider across 2 OpenAPI documents. Consistent with pagination — this is inferred from where t | 2 | 1 |
|
x-pingidentity-paginatedresponse
vendor |
`x-pingidentity-paginatedresponse` appears on operations. Its value is a boolean flag. Used by a single provider across 1 OpenAPI document. It sits in the `x-pingidentity-` namespace, so its meaning i | 2 | 1 |
| x-offset | `x-offset` appears on header objects. Its value is a structured object. Used by a single provider across 1 OpenAPI document. Consistent with pagination — this is inferred from where the key appears an | 1 | 1 |