This page describes the functions of our HTTP API: pre-rendering, screenshots, PDFs, and scraping.
Each function targets a specific URL and is accessible through GET requests.
You can configure the options via HTTP headers.

API paths and functionality:

1. /$url, for pre-rendering
2. /screenshot/$url, for screenshots
3. /pdf/$url, for PDFs
4. /scrape/$url, for scraping

Open API Spec:

• /.well-known/open-api.yaml

AI LLM (ChatGPT) Spec:

• /.well-known/ai-plugin.json

Notes:

For the target $URL, include it as part of the path without re-encoding or re-escaping beyond what's required for a standard browser URL input. Both UTF-8 encoding and percent-encoding are acceptable

The pre-rendering API is designed for webserver middleware. A faster, separate endpoint is available for scraping purposes without pre-rendering features.

The Screenshot, PDF, and Scrape APIs are accessible via simple HTTP GET requests

The scrape endpoint serializes HTML just like the pre-render endpoint, but without the injected JavaScript, preloaded state, custom serialization, and proxy functionality, making it up to twice as fast for HTML serialization. If you're looking to scrape JavaScript apps (or plain old HTML apps), this is your endpoint.