> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fingerprint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring resources

> The Dashboard allows you to manage all the resources and settings that govern how your Fingerprint implementation operates.

## API keys

API keys are necessary for your Fingerprint setup. Primarily to be able to identify visitors and generate visitor IDs, but also interact with other Fingerprint APIs and features.

To manage API keys, go to **Dashboard** > [**API keys**](https://dashboard.fingerprint.com/api-keys).

<Frame>
  <img src="https://mintcdn.com/fingerprint/oFZK_WZRNHYkOW2F/images/CleanShot-2026-05-28-at-13.51.22@2x.png?fit=max&auto=format&n=oFZK_WZRNHYkOW2F&q=85&s=5bed1d7ef3625a9763e3e739ee3c0877" alt="Clean Shot 2026 05 28 At 13 51 22@2x" width="2788" height="1114" data-path="images/CleanShot-2026-05-28-at-13.51.22@2x.png" />
</Frame>

| Keys                      | Description                                                                                                                                                                              |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Public**                | Used to make **client-side requests** to identify visitors and generate the visitor ID. Used in the [browser](/docs/identify-visitors) or in [mobile apps](/docs/mobile-identification). |
| **Server API**            | Used to make **server-side requests** to the Fingerprint [Server API](/reference/server-api) to securely obtain visitor and request information.                                         |
| **Management API**        | Used to access the [**Management API**](/reference/management-api), allowing management of dashboard resources.                                                                          |
| **Sealed Client Results** | Used to enable **Sealed Client Results** to [encrypt client-side payloads](/docs/sealed-client-results).                                                                                 |
| **Proxy**                 | Used to authenticate with third-party **proxy integrations** which allow you to [evade ad blockers](/docs/protecting-the-javascript-agent-from-adblockers).                              |

To monitor API key usage, throttling, and latency, see [API key monitoring](/docs/health#api-key-monitoring).

## Request filtering

Request filtering is a feature that enables you to filter out unwanted identification requests using specific rules. On the Dashboard, you can **manage filtering rules** by adjusting which events should be allowed or denied.

To learn more information, see [request filtering](/docs/request-filtering).

To manage webhooks, go to **Dashboard** > [**Security**](https://dashboard.fingerprint.com/traffic-rules).

## Webhooks

Webhooks allow you to receive an HTTP request to your server with Fingerprint results for every identification event the moment it happens. On the Dashboard, you can **manage webhooks** and monitor their activity.

To learn more information, see [webhooks](/docs/webhooks).

To manage webhooks, go to **Dashboard** > [**Webhooks**](https://dashboard.fingerprint.com/webhooks).

To inspect webhook delivery attempts and diagnose failures, see [Webhook monitoring](/docs/health#webhook-monitoring).

## Custom subdomains

By using a custom subdomain, Fingerprint cookies are treated as "first-party", which increases identification accuracy while also allows you to avoid ad blockers. On the Dashboard, you can **register your subdomains** and manage their certificates.

To learn more information, see [Custom subdomain setup](/docs/custom-subdomain-setup).

To manage subdomains, go to **Settings** > [**Subdomains**](https://dashboard.fingerprint.com/subdomains).

## Proxy integrations

Proxy integrations are an alternative to custom subdomains, they allow you to proxy requests to Fingerprint through your own domain. Our cookies are treated as "first-party", which increased identification accuracy while allowing you to avoid ad blockers. On the Dashboard, you can **setup proxy integrations** and monitor their status and activity.

To learn more information, see [Evading ad blockers with proxy integrations](/docs/protecting-the-javascript-agent-from-adblockers).

To manage proxy integrations, go to **Dashboard** > [**Libraries & integrations**](https://dashboard.fpjs.sh/integrations/active)

## Suspect Score

Suspect Score is an easy way to integrate Smart Signals into your fraud protection workflow. It is a weighted representation of all Smart Signals present in the payload that helps identify suspicious activity. On the Dashboard, you can configure the **weights for suspect scoring** by adjusting for each detected Smart Signal.

To learn more information, see [Suspect Score](/docs/suspect-score).

To manage suspect score weights, go to **Dashboard** > **Smart Signals** > [**Suspect Score**](https://dashboard.fpjs.sh/suspect-score)

***

[Viewing analytics](/docs/analytics)