> For the complete documentation index, see [llms.txt](https://docs.truvera.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truvera.io/truvera-workspace/creating-api-keys-and-webhook-endpoints.md).
# Creating API keys and webhook endpoints
## Creating API keys
To create an API key, under the Developer menu item, click API Keys. Then select Create API key.
Under Whitelisted IP’s, you have the option to add additional security by configuring IP's that are allowed to access your services
{% hint style="warning" %}
Keep your API key safe, for security reasons it will not be shown again. Please do not share this key. If you forget your API key, you will need to delete the existing key and create a new one.
{% endhint %}
For more information about API [See API documentation](/truvera-api.md)
## Webhooks endpoints
You can add or modify webhook endpoints that will send events when issuing or when transactions occur. Under Developer, select Webhook and click Add Endpoint on the top right.
Fill in the Webhook details and click Create Webhook.
[](https://downloads.intercomcdn.com/i/o/797831076/f27e685f76d0e00a209759cd/6356fc0a5432fa812b8eaea6_2-Webhook+details.png)
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.truvera.io/truvera-workspace/creating-api-keys-and-webhook-endpoints.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
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.
