SavePage.io API

Development / API Key Intermediate HTTPS CORS
Varies by plan (check documentation)

Overview

SavePage.io provides a RESTful API for capturing full-page screenshots of any desktop or mobile website. Simply send the target URL along with your API key, and receive a screenshot image or a URL pointing to the rendered page. It supports various output formats and viewport sizes, making it useful for monitoring, archiving, or generating visual previews.

Beginner Tip

Pass the capture_url parameter as a URL-encoded string and specify the format (png or jpeg) in your request. Start with desktop screenshots before experimenting with mobile viewports.

Available Data

SavePage.io data via REST API

Example Response

JSON Response
{
  "id": "Dwu85P9SOIk",
  "urls": {
    "full": "https://images.unsplash.com/photo-...",
    "regular": "https://images.unsplash.com/photo-...?w=1080",
    "thumb": "https://images.unsplash.com/photo-...?w=200"
  },
  "width": 4000,
  "height": 3000,
  "user": {
    "name": "John Doe",
    "username": "johndoe"
  }
}

Field Reference

url The URL of the captured screenshot stored on the server.
status Status of the screenshot capture request.
timestamp ISO 8601 timestamp of when the screenshot was taken.

Implementation Example

Request
const url = "https://www.savepage.io/";
// Replace headers or query params with the values required by this API.
const response = await fetch(url, {
  headers: {
  "X-API-Key": "YOUR_API_KEY"
  }
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

401 Unauthorized Missing or invalid API key in the request
Ensure your API key is passed as the apikey query parameter. Check your dashboard for the correct key.
Timeout / empty screenshot The target website takes too long to load or blocks headless browsers
Try increasing the timeout parameter if supported, or test with a simpler URL like https://example.com first.
400 Bad Request The target URL is not properly URL-encoded or is missing the protocol
Always include https:// or http:// in the URL and encode special characters.

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth API Key
HTTPS REQUIRED
CORS YES
Category Development
Difficulty Intermediate
Verified: 2026-04-04

Related Tags

Similar APIs

View All →