Upcoming Change: IPv6 Support and IP Allowlist Update Required

On August 12, 2025, Bridge will be updating our API infrastructure to support IPv6, the next-generation Internet Protocol. As a result, applications that rely on IP restrictions will need to update their allowlists to include IPv6 addresses to avoid disruptions.

What You Need to Know

  • IPv6 is now preferred over IPv4 in many modern systems and networks.
  • If your application is configured to allow only IPv4 addresses, requests from IPv6-enabled environments may be blocked if those IPs aren’t listed.
  • To maintain uninterrupted access, you must update your allowlist to include both IPv4 and IPv6 addresses.
  • Applications that do not rely on IP allowlists will not be affected.

What You Need to Do

  1. Log into bridgedataoutput.com and navigate to API Access > Application Settings. 
  2. Review your application’s existing IP restrictions.
  3. Add any relevant IPv6 addresses to the allowlist before August 12.
  4. Be sure to do this for all applications under your Bridge account by using the application switcher menu in the top-right corner of your dashboard.
  5. If you’re unsure which IPv6 addresses to include, contact your network administrator or hosting provider.

Example

  • IPv4: 192.0.2.1
  • IPv6: 2001:0db8:85a3:0000:0000:8a2e:0370:7334

Need Help?

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 our support team at support@bridgeinteractive.com.

Thank you for keeping your Bridge API integration secure and future-ready!

Upcoming Change to $top and Page Size Behavior on Bridge API v3 Endpoint

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.