> For the complete documentation index, see [llms.txt](https://docs.sentiance.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sentiance.com/getting-started/insights-control-tower/developer-dashboard/api-keys.md).

# API Keys

### Generate API Key

ICT allows developers to generate a user API Key and communicate with the Sentiance Backend:

1. Login to **Insights Control Tower**
2. Navigate to the "**Developer**" tab
3. Under "**API Keys**", click on button "Create API Key"
4. Choose a name for this new API Key, the name is for visual purposes only and has no operational impact. Choose a name that would help you identify the key.
5. Select the permission scopes. These scopes define what operations an API Key can perform. <br>

   <table><thead><tr><th width="282.80029296875">Scope name</th><th>Scope description</th></tr></thead><tbody><tr><td><strong>USER_READ</strong></td><td>Use this scope to read user data. </td></tr><tr><td><strong>USER_DELETE</strong></td><td>Use this scope to delete a user along with all historical data.</td></tr><tr><td><strong>USER_LINK</strong></td><td>Use this scope to perform <br>User Creation &#x26; Authentication.</td></tr><tr><td><strong>OFFLOADS_READ</strong></td><td>Use this scope to list Offloads available for download.</td></tr><tr><td><strong>OFFLOADS_GENERATE_URL</strong></td><td>Use this scope to generate URLs at which offloads can be downloaded.</td></tr><tr><td><strong>FAKE_DATA_INSERT</strong></td><td>Use this scope to inject fake.<br>Engagement platform only!</td></tr></tbody></table>
6. Click on create API Key.
7. The API key is now available for copy or download. Please copy and store it securely. For security reasons, this API key is displayed only once and cannot be viewed again.
8. After creation success, store your API Key in a safe environment and update your backend system to include the newly created API Key

{% hint style="danger" %}
**Do NOT share your API Keys and keep your credentials in a secure environment.** \
**Never include your API Keys in you client side application**
{% endhint %}