Data Centers

Browser7 operates multiple data centers globally to provide low-latency access and data residency options.

Default Endpoint (Recommended)

https://api.browser7.com/v1

The default endpoint uses geo-DNS routing to automatically direct your requests to the nearest available data center based on your geographic location. This provides:

• Optimal latency - Automatic routing to the closest data center
• High availability - Automatic failover if a region is unavailable
• Simplicity - No need to manage regional endpoints

We recommend using the default endpoint for most use cases.

Regional Endpoints

For advanced scenarios where you need to explicitly target a specific data center, regional endpoints are available:

North America

https://ca-api.browser7.com/v1

• Location: Canada
• Coverage: Optimized for North American traffic
• Use case: When you require data processing within North American jurisdiction

Europe

https://eu-api.browser7.com/v1

• Location: European Union
• Coverage: Optimized for European traffic
• Use case: When you require GDPR compliance or data processing within EU jurisdiction

Proxy Location and Data Center Selection

By default, each data center automatically selects proxy locations with under 20ms latency for optimal performance. This means:

• European data center - Automatically uses European proxies by default
• North American data center - Automatically uses North American proxies by default

Custom Proxy Locations

If you explicitly specify a countryCode or city parameter while using a regional endpoint, choose locations near that data center for best performance:

European endpoint (eu-api.browser7.com):

• ✅ Optimal: European countries (UK, DE, FR, IT, ES, NL, etc.)
• ⚠️ Higher latency: US, CA, Asia-Pacific countries

North American endpoint (ca-api.browser7.com):

• ✅ Optimal: US, CA, MX
• ⚠️ Higher latency: European and Asia-Pacific countries

Example of optimal configuration:

// European data center + European proxy location
const euClient = new Browser7({
  apiKey: 'b7_your_api_key',
  baseUrl: 'https://eu-api.browser7.com/v1'
});

await euClient.render('https://example.com', {
  countryCode: 'DE'  // Germany - close to EU data center
});

Example of suboptimal configuration:

// European data center + North American proxy (higher latency)
const euClient = new Browser7({
  apiKey: 'b7_your_api_key',
  baseUrl: 'https://eu-api.browser7.com/v1'
});

await euClient.render('https://example.com', {
  countryCode: 'US'  // US proxy far from EU data center - adds latency
});

When to Use Regional Endpoints

Consider using a regional endpoint when:

1. Data Residency Requirements - Your organization requires data to be processed in a specific geographic region for compliance reasons
2. Consistent Routing - You want to ensure all requests go to the same data center regardless of where they originate
3. Testing - You're testing region-specific behavior or debugging location-based issues
4. Proximity to Target Proxies - Your renders primarily use proxies in a specific region

SDK Configuration

All Browser7 SDKs support custom base URLs for regional endpoints:

Node.js

const Browser7 = require('browser7');

// Default (geo-DNS)
const client = new Browser7({ apiKey: 'b7_your_api_key' });

// European endpoint
const euClient = new Browser7({
  apiKey: 'b7_your_api_key',
  baseUrl: 'https://eu-api.browser7.com/v1'
});

Python

from browser7 import Browser7

# Default (geo-DNS)
client = Browser7(api_key='b7_your_api_key')

# North American endpoint
ca_client = Browser7(
    api_key='b7_your_api_key',
    base_url='https://ca-api.browser7.com/v1'
)

PHP

use Browser7\Browser7Client;

// Default (geo-DNS)
$client = new Browser7Client('b7_your_api_key');

// European endpoint
$euClient = new Browser7Client(
    'b7_your_api_key',
    'https://eu-api.browser7.com/v1'
);

Performance Considerations

Latency

Using the default endpoint typically provides the lowest latency since requests are routed to the nearest data center. Explicitly targeting a distant regional endpoint may increase latency.

Example latencies from different locations:

Your Location	Default Endpoint	ca-api (Canada)	eu-api (Europe)
New York, US	~20ms (auto-routed to CA)	~20ms	~80ms
London, UK	~15ms (auto-routed to EU)	~75ms	~15ms
Tokyo, JP	~30ms (auto-routed to nearest)	~120ms	~200ms

Latencies are approximate and may vary based on network conditions

Render Location vs API Endpoint

The API endpoint location is separate from the render location:

• API Endpoint - Where you send your API requests (this page)
• Render Location - Where the browser renders the page (controlled by countryCode and city parameters)

You can render pages from any country regardless of which API endpoint you use. However, for optimal performance, match your data center to your most commonly used proxy regions.

Best Practices

1. Start with the default - Use api.browser7.com unless you have a specific reason to use a regional endpoint
2. Match regions when possible - If you frequently render from European locations, consider using the European endpoint
3. Test latency - If you're concerned about performance, measure actual latency from your servers to each endpoint
4. Document your choice - If you use a regional endpoint, document why in your code or configuration
5. Monitor availability - While rare, regional endpoints may have scheduled maintenance

Data Residency

If your use case requires data residency compliance:

• European endpoint (eu-api.browser7.com) - API requests and metadata are processed within the European Union
• North American endpoint (ca-api.browser7.com) - API requests and metadata are processed within Canada

Note that render data (the websites you're scraping) may originate from any country depending on your countryCode parameter.

Support

If you have questions about which endpoint to use for your specific compliance or performance requirements, contact support@browser7.com.