Support for multiple API keys

You can now use multiple API keys to the access ScreenshotOne API.

Changelog1 min read

Written by

Dmytro Krasun

Published on

Many ScreenshotOne customers asked to support more than one API key to access the API. Some need that for local development, some for testing or to separate different environments, and some for security reasons.

It took us some time to implement this feature and test everything, but now it is available.

Since today you can create and use multiple API keys to access the ScreenshotOne API. Check out the access page in the dashboard:

Multiple API keys in the dashboard

A few notes:

  1. Concurrency limit is shared between all API keys.
  2. Quota is shared between all API keys.
  3. You can regenerate or delete any API key. But cached screenshots might be still available.
  4. At least one API key is required to exist. You can’t delete all of them.

If you have any questions or need any assistance, please, reach out at support@screenshotone.com.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
Fail if there is nothing to click on

Fail if there is nothing to click on

A new option has been added to fail or not to fail the screenshot rendering if there is nothing to click on.

Read more

1 min read

Updated the official Python SDK

Updated the official Python SDK

Fixed shared options and metadata results, unified API errors, and synchronized option helpers with the screenshot API documentation.

Read more

1 min read

Faster dashboard metrics

Faster dashboard metrics

Dashboard usage and error metrics now load faster as ScreenshotOne continues operating millions of screenshots every month.

Read more

1 min read

Automate website screenshots

Exhaustive documentation, ready SDKs, no-code tools, and other automation to help you render website screenshots and outsource all the boring work related to that to us.