Articles on: API

Preconfigured request settings

We are excited to announce a new time-saving feature: Preconfigured Request Settings!

Many of our users have asked for an easier way to manage request settings, and we’ve listened. With this new feature, you can now preconfigure settings for any website and reuse them whenever needed—eliminating the hassle of manually entering them every time.

What is Preconfigured Request Settings?



Preconfigured Request Settings allow you to save commonly used settings for specific websites. Once saved, these settings can be quickly applied in your code, or on our request builder, streamlining your workflow and reducing repetitive data entry.

Why Use This Feature?



Save Time: No more re-entering the same settings for frequently used websites.

Consistency: Ensure requests are configured correctly every time, especially when dealing with JS Scenarios or extraction rules.

Convenience: Easily switch between different preconfigured settings as needed.

How to Create Preconfigured Request Settings



Navigate to the Request Builder – After logging into your ScrapingBee account.

Setup the settings – Including proxies, JS Scenarios, extraction rules and the URL itself.

Click on Save the request:
Save the request

Insert a unique name, and a description:
Form fields
Click on Create – You have now created a configuration that can help you reproduce request settings with ease!

How to Use Preconfigured Request Settings



Through requests / code:

Once a preconfigured request has been created, you can use it by running your request to ScrapingBee's endpoint, with the setting scrape_config containing the unique name that you picked for this configuration.

A sample request URL for that will look like this:

https://app.scrapingbee.com/api/v1?api_key=Your-API-Key&scraping_config=Configuration-Name

In our previous example, the URL would be: https://app.scrapingbee.com/api/v1?api_key=Your-API-Key&scraping_config=ScrapingBee-Blog-Configuration

This will automatically get ScrapingBee to scrape our blog, using the settings we previously set.

If you want to replace the URL, and keep the same configuration, you can simply add the url parameter to your request, so the final request URL will be:

https://app.scrapingbee.com/api/v1?api_key=Your-API-Key&scraping_config=ScrapingBee-Blog-Configuration&url=https://scrapingbee.com

You can also overwrite any existing parameter in the configuration, just like the url setting, by adding it to your request URL.

For example, our previous configuration for ScrapingBee's blog uses premium proxies, but we can disable them by adding premium_proxy=False to our request URL:
https://app.scrapingbee.com/api/v1?api_key=Your-API-Key&scraping_config=ScrapingBee-Blog-Configuration&premium_proxy=False

Through the request builder:

You can also use the preconfigured requests on our request builder by clicking on Apply a preconfigured request, then choose the one you'd like to use:

Apply Preconfigured Request - Request Builder
Once you click on it, you will notice that the settings have been updated, and that the configuration has been set correctly:

Preconfigured Request - Request Builder

How to Remove Preconfigured Request Settings



You can remove preconfigured request settings by following these steps:

Click on "My HTML Requests" on the sidebar

Check the configurations you'd like to delete

Click on "Delete all selected requests"

Delete Preconfigured Requests
You can also delete individual configuration by clicking on the three vertical dots icon, then clicking "Delete":



How to Update Preconfigured Request Settings



To update a preconfigured request, you can use the request builder:

Make sure that the configuration is loaded:


Make any changes you'd like on the settings, including the URL, JS Scenarios, proxies, etc...

Click on "Save the request":


Make sure that "Update the request" is selected, then click on "Update":



We hope this feature makes your experience more efficient and enjoyable. If you have any questions or feedback, feel free to reach out to our support team!

Updated on: 14/02/2025

Was this article helpful?

Share your feedback

Cancel

Thank you!