---
sourceDocument: Australia Telecom Service Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/telecom-service-ops

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Telecom Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Page limits for Meraki pull connector endpoints

# Page limits for Meraki pull connector endpoints {#ariaid-title1}

Release version: Australia  
Updated November 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The Meraki pull connector paginates API requests so that all records are retrieved for large organizations. The page size is set per endpoint to match each endpoint's maximum supported value in the Meraki API v1.

## How pagination works {#meraki-pull-connector-page-limits__section_pagination_behavior}

The connector follows the pagination links returned in the `Link`
header (`rel=next`) until all pages are consumed, then aggregates the
data from every page. The page size is controlled by the `perPage`
parameter, which is configured per endpoint as shown in the following table.
{#meraki-pull-connector-page-limits__table_perpage__entry__2}

| Endpoint | Items per page (`perPage`) |
|-|-|
| `/organizations` | 1000 |
| `/organizations/{orgId}/networks` | 1000 |
| `/organizations/{orgId}/devices` | 1000 |
| `/organizations/{orgId}/appliance/uplink/statuses` | 1000 |
| `/organizations/{orgId}/appliance/uplinks/usage/byNetwork` | 20 |
| `/organizations/{orgId}/appliance/vpn/stats` | 300 |
| `/organizations/{orgId}/switch/ports/statuses/bySwitch` | 20 |
| `/organizations/{orgId}/configurationChanges` | 1000 |
[Table 1. Endpoint page sizes]

{#meraki-pull-connector-page-limits__table_perpage}

## Endpoints without a page limit {#meraki-pull-connector-page-limits__section_single_request_endpoints}

Endpoints that do not have a configured `perPage` limit (for example,
`/devices/{serial}/appliance/performance` and
`/networks/{networkId}/appliance/trafficShaping/uplinkBandwidth`) are
treated as single requests. These endpoints return all of their data in one
response, so the `Link` header is absent and the pagination loop
exits after the first page.