ScreenshotOne Integration
ScreenshotOne + BytesFlows: residential IP routing for developer pipelines
ScreenshotOne renders web page screenshots — configuring BytesFlows residential proxies in your ScreenshotOne API options allows you to render geo-restricted pages or bypass bot blocks during image capture.
ScreenshotOne proxy configuration example
Seamless integration with BytesFlows endpoints using standard proxy auth.
const axios = require('axios');
// Request ScreenshotOne with BytesFlows proxy parameters
const params = {
access_key: 'YOUR_ACCESS_KEY',
url: 'https://protected-site.com',
proxy: 'http://YOUR_USER:YOUR_PASS@p1.bytesflows.com:8001'
};
async function takeScreenshot() {
const res = await axios.get('https://api.screenshotone.com/take', { params, responseType: 'arraybuffer' });
console.log('Screenshot captured via residential proxy, size:', res.data.length);
}
takeScreenshot();Replace YOUR_USER and YOUR_PASS with your BytesFlows sub-user credentials from the dashboard.
How ScreenshotOne routes through BytesFlows
Standard proxy forwarding ensures every request exits via clean residential IPs.
ScreenshotOne Request
The application or script initiates a request configured with BytesFlows proxy host and credentials.
Authentication & Geo
BytesFlows gateway verifies credentials and resolves geo-targeting requirements (-cc-US, -cc-GB, etc.).
Residential Exit Node
The request is forwarded through an authentic home broadband IP from our 65M+ pool.
Target Destination
The target API or website receives the request with zero datacenter signals or rate limiting.
Supports both rotating mode (new IP per request) and sticky sessions (same IP up to 60 minutes).