Support for multiple API keys

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

1 min read

Written by

Dmytro Krasun

Published on

Support for multiple API keys

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
Remove organization members

Remove organization members

Improvements to the organization management.

Read more

1 min read

Use cases in the ScreenshotOne playground

Use cases in the ScreenshotOne playground

Having documentation and code examples is great, but not enough to allow developers to quickly integrate the API and assess all available features of the ScreenshotOne API.

Read more

1 min read

Improving performance and stability by consolidating validation and access check logic in the API gateway

Improving performance and stability by consolidating validation and access check logic in the API gateway

For the past few days, I have been working on improving the stability and performance of the ScreenshotOne API. I started from low-hanging fruits—moving validations and access key management from rendering services to ScreenshotOne's API gateway. The API will be more stable and performant as a result. If you are curious why, please continue reading.

Read more

2 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.