SlicingDice Documentation

SlicingDice - The All-in-One Solution Documentation

Welcome to the SlicingDice documentation. You'll find comprehensive guides and documentation to help you start working with SlicingDice as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Guides

Database access whitelist

First time checking our docs? You might want to start with the right foot by reading our Documentation Guide first.

By default, your database keys can be used from any computer with Internet access.

However, there might be situations where you want to strictly control which IP addresses or website domains can use a determined database key.

For example, if you deploy a website and want to monitor its visits and page views by sending data to SlicingDice, it would be more secure if your write database key was limited for requests originating from your website (domain).

Using the SlicingDice Control Panel, you can define a whitelist, containing any IP address or website domain that can make API requests using your database keys.

There are two ways of using whitelists on SlicingDice, on the database configuration or on the Custom Database Keys configuration.

Database whitelist explained by video

Watch this quick video below to learn how to configure a whitelist for a database.

Database whitelist

In order to add or edit the whitelist for a database, simply access the SlicingDice Control Panel and click on the database section on the main menu. Select the database you want to configure the whitelist and click to edit it.

Any IP address or website domain you add to the whitelist, will be applied to your database's read, write and master keys.

Custom Database Keys whitelists

In order to add or edit the whitelist for a custom database key, simply access the SlicingDice Control Panel, click to edit the database for which you want to create the custom key and then click on the custom database key section.

Each custom database key can have their own whitelist, completely independent from the general database whitelist or other custom database key whitelists.