On July 29, 2025, we’ll be making a change only on our v3 endpoint to our default behavior regarding $top and page size.
On v3, in line with the OData specification, $top is treated as the total collection size, not individual page size. Clients may specify a given page size with the maxpagesize header. Our current default page size is 10 with a maximum value of 200.
Starting July 29, if a client includes a $top parameter without also specifying a maxpagesize preference, the Bridge API v3 endpoint will return up to $top records in the response, capped at 200 (the maximum page size).
To illustrate, if a client is issuing the following requests to the v3 endpoint without a maxpagesize preference header, here is how the responses will be impacted:
| Request | Current v3 Response | Coming v3 Response |
| $top=5 | Returns 5 records | Returns 5 records |
| $top=100 | Returns 10 records (default page size) | Returns 100 records |
| $top=1000 | Returns 10 records (default page size) | Returns 200 records (capped at max limit) |
We’ve already notified by email any users with applications making Bridge API requests that may be impacted by this change. If you have any questions, please contact the Bridge API support team at support@bridgeinteractive.com.