# Quick Start

### Creating an API Key

API keys are how your Redis compatible client can connect to Thiicket; they also represent seperate distinct namespaces with their own eviction policies and similar

In the Thiicket [dashboard](https://dash.thiicket.com/), click the green plus icon above the 'API Keys' table

![](https://3598615042-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDoM-iZkdQjnW5MlV15%2F-MDoM1Z72WrmModuHdcH%2F-MDoNLuqOZuZThNQBgAF%2Fimage.png?alt=media\&token=635833b6-1853-4b74-82a2-138b7b922d9e)

This will open a message box asking you to configure your new API key

![](https://3598615042-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDoM-iZkdQjnW5MlV15%2F-MDoM1Z72WrmModuHdcH%2F-MDoNddZ5Fwr7qnDOCW2%2Fimage.png?alt=media\&token=958ce187-3e64-4cbb-a9b6-7259820c8786)

For this tutorial, set memory limit to 10485760 and the eviction policy to "Random". Once entered, select "Create" and a new API key will be presented

Open a Terminal / bash environment and set API\_KEY to the value from above. Next let's connect to Thiicket using your new API key

### Connecting to Thiicket

When connecting to Thiicket, you have two options: explicitly select a region or let us route you to the nearest geographic region. For this tutorial we'll use the auto-routing feature

```
$ redis-cli -h connect.thiicket.com -a $API_KEY
```

Next, let's try some basic Redis commands

```bash
connect.thiicket.com:6379> SET myfirstkey "Hello world!"
OK
connect.thiicket.com:6379> GET myfirstkey
"Hello world!"
connect.thiicket.com:6379> 
```

{% hint style="info" %}
 Thiicket supports most Redis commands, see the full list [here](https://docs.thiicket.com/supported-commands)
{% endhint %}

### Understanding Namespaces

Create a new API key as by the above process, and set it in an environment variable called API\_KEY\_2

```bash
$ redis-cli -h connect.thiicket.com -a $API_KEY_2
connect.thiicket.com:6379> GET myfirstkey
(nil)
connect.thiicket.com:6379> SET myfirstkey "I'm in a different namespace!"
OK
connect.thiicket.com:6379> GET myfirstkey
"I'm in a different namespace!"

$ redis-cli -h connect.thiicket.com -a $API_KEY
connect.thiicket.com:6379> GET myfirstkey
"Hello world!"
```

As the above example shows, each API key is completely distinct from the other and each have their own namespace. Keys in different namespace cannot be accessed and updating a key in one does not affect the other

{% hint style="info" %}
Namespaces are isolated at the regional level, two clients connecting to different regions will not have access to the same data
{% endhint %}