Support for multiple API keys

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

Changelog 1 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
Added a "copy page" button in documentation

Added a "copy page" button in documentation

You can now copy the page content as Markdown for LLMs and more.

Read more

1 min read

Available in Context7

Available in Context7

ScreenshotOne documentation is now available in Context7.

Read more

1 min read

An improved screenshot history page

An improved screenshot history page

Daily, I work as hard as I can to ensure that ScreeenshotOne is the best screenshot API out there possible. But I rarely share updates but trust me, a ton of them might go unnoticed. Let's fix this situation.

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.