> For the complete documentation index, see [llms.txt](https://thirdfi.gitbook.io/thirdfi.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thirdfi.gitbook.io/thirdfi.org/product/developer-dashboard.md).

# Developer Dashboard

### Developer Portal

This helps developers to monitor all the API requests and activity logging based on their API integration. Also, it supports sandbox data during their development, which is useful for verifying the expected result from various products.

Also, developers can manage API key and webhook-related functions on the dashboard, so it helps developers only focus on the API integration. 

### API key and webhook management

API and secret keys are useful for accessing and getting authenticated with ThirdFi private APIs.

Therefore, developers are required to generate the API key and secret key on the Developer Portal. They can set up the whitelisted IP addresses and some permission controls for a specific API key. 

Also, developers can configure webhook endpoints to receive the ThirdFi webhook event.

#### Features:

* Create a new API key and secret key
* Assign permissions and whitelist IP address to the API key
* Setup Webhook endpoints


---

# 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://thirdfi.gitbook.io/thirdfi.org/product/developer-dashboard.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.