Skip to main content

Overview

The Scrapengine Proxy allows you to use Scrapengine as a standard HTTP/HTTPS proxy server. This is ideal for integrating with existing tools, libraries, or applications that support proxy configuration. Simply point your HTTP client to our proxy endpoint and authenticate using your API key.
The proxy interface provides the same scraping capabilities as the REST API but through a standard proxy protocol that works with any HTTP client.

Proxy Endpoint

Authentication

Authentication is done via HTTP Basic Auth where:
  • Username: Any value (e.g., scrape)
  • Password: Your Scrapengine API key

Quick Start

Configuration Headers

Control scraping behavior by passing custom headers with your request. These headers are parsed by the proxy and configure how the scraping job is executed.

Examples with Headers

Enable JavaScript Rendering

Scrape pages that require JavaScript to load content:

Get Markdown Output

Convert the scraped content to clean Markdown:

Geo-Targeted Scraping

Scrape from a specific geographic location:

Multiple Options Combined

Combine multiple options for advanced scraping:

POST Requests

Send POST requests through the proxy:

Response Headers

The proxy returns the following headers with each response:

Error Handling

Authentication Errors

If authentication fails, you’ll receive a 407 Proxy Authentication Required response:
Solutions:
  • Verify your API key is correct
  • Ensure the password field contains your API key
  • Check that your API key has not expired

Common HTTP Errors

Error Response Format

Proxy vs REST API

Use the REST API if you need AI-powered data extraction with schemas or prompts. Use the Proxy for simple scraping or when integrating with existing tools that support proxy configuration.

Use Cases

  • Browser automation tools: Configure Puppeteer, Playwright, or Selenium to use Scrapengine as a proxy
  • CLI tools: Use with wget, curl, or other command-line HTTP clients
  • Existing applications: Add scraping capabilities without code changes
  • Testing tools: Route traffic through Scrapengine for web testing
  • Scripting: Simple one-liner scraping in shell scripts

Best Practices

Always prefer HTTPS URLs for better security and reliability when scraping.
JavaScript rendering (x-scrapengine-render: true) uses more resources. Only enable it for pages that require JavaScript to load content.
Set appropriate timeouts in your HTTP client. Scraping can take longer than typical API calls, especially with rendering enabled.
Check the x-remaining-credits header in responses to monitor your usage and avoid unexpected interruptions.