Screenshot API error ยท HTTP 403

Key of another product

key_not_allowed_for_product

The API key is valid, but for another EverAPI product (currencyapi, ipbase, …). Each product has its own keys.

How to recognize it

The API answers with status 403 and a JSON body with the message and the error.code key_not_allowed_for_product, for example:

HTTP/1.1 403
Content-Type: application/json

{
  "error": {
    "code": "key_not_allowed_for_product",
    "message": "You cannot access screenshotbase with this key"
  },
  "message": "You cannot access screenshotbase with this key"
}

Common causes

  • A key from another EverAPI dashboard used for screenshotbase.

How to fix it

  1. Use the key from the screenshotbase dashboard, or create a screenshotbase account with the same email address.

Billing

Not billed: a request answered with this error does not count against your quota.

Every response carries an X-Request-Id header. If this page does not explain the error, write to support@screenshotbase.com with that id. All statuses: status codes.

Other API errors

Screenshot API

Take screenshots from your code

screenshotbase renders any website in a real browser and returns the image: full page or viewport, any device size, retina, from 100+ countries, with cookie banners and ads hidden.

/v1/take documentation Screenshot API All documentation

300 free screenshots every month. No credit card required.

GET https://api.screenshotbase.com/v1/take?url=https://example.com&full_page=true

# Response: the image (PNG, JPG, WebP or GIF)
curl -G "https://api.screenshotbase.com/v1/take" \
  --data-urlencode "url=https://example.com" \
  -d viewport_width=1280 -d viewport_height=800 \
  -d format=png \
  -H "apikey: YOUR-API-KEY" \
  -o screenshot.png

More free tools

Start using our Screenshot API for free today!

Get 300 requests / month for free