> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/dt-fairbid/reporting/reporting-api/api-authentication.md).

# API Authentication

You must use an authentication token to interact with DT Fairbid APIs. To obtain an authentication token, send your verification key through the appropriate authentication endpoint.

* [DT FairBid Management API](/dt-fairbid/advanced-configurations/dt-fairbid-management-api.md) - Allows publishers to create and maintain all settings required to monetize their apps with ads.
* [DT FairBid Reporting API](/dt-fairbid/reporting/reporting-api/dt-fairbid-reporting-api.md) - Gives access to all the reporting data from the monetization ad units. You can query multiple metrics such as revenue and impressions and filter by the available dimensions.
* [DT FairBid User Level Reporting API](/dt-fairbid/reporting/reporting-api/dt-fairbid-user-level-reporting-api.md) - Gives access to reporting data to measure all revenue generated from individual device users. Use this information to optimize retargeting campaigns and accurately measure user lifetime value (LTV).

## Obtaining Verification Keys

To obtain an authentication token, you must provide the appropriate verification key for each API.

**To locate your verification keys:**

1. Log in to the [DT Console](https://console.fyber.com/), and click your user name in the left-hand menu.
2. Click **User Profile**.

<div align="left" data-with-frame="true"><img src="/files/8qAOyyVkepxJDZYVOWtZ" alt="" width="265"></div>

The page that opens shows three types of credentials:

3. Consult the table below to identify which key to use:

| DT FAIRBID API                                                                                                    | NAME IN DT CONSOLE                   | VERIFICATION KEYS                                            |
| ----------------------------------------------------------------------------------------------------------------- | ------------------------------------ | ------------------------------------------------------------ |
| [DT FairBid Management API](/dt-fairbid/advanced-configurations/dt-fairbid-management-api.md)                     | Management API - Credentials         | <p>- Client ID<br>- Client secret</p>                        |
| [DT FairBid Reporting API](/dt-fairbid/reporting/reporting-api/dt-fairbid-reporting-api.md)                       | Advanced Reporting API - Credentials | <p>- Client ID<br>- Client Secret</p>                        |
| [DT FairBid User Level Reporting API](/dt-fairbid/reporting/reporting-api/dt-fairbid-user-level-reporting-api.md) | Basic Reporting API - Credentials    | <p>- Publisher ID<br>- Consumer Key<br>- Consumer Secret</p> |

## Generate New Keys

You should generate new verification keys on a regular basis. In order to generate new keys, you must first revoke the current keys.

**To generate new verification keys:**

1. Log in to the [DT Console](https://console.fyber.com/), and click your user name in the left-hand menu.
2. Click **User Profile**.
3. For the verification keys you want to re-generate, click **Revoke**.

<div align="left" data-with-frame="true"><img src="/files/ITwJuMUEviI07iGIHYvL" alt=""></div>

4. Click **Generate New Keys**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digitalturbine.com/dt-fairbid/reporting/reporting-api/api-authentication.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.