> For the complete documentation index, see [llms.txt](https://dg-market.gitbook.io/dg-live/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dg-market.gitbook.io/dg-live/business-manager/api-auth.md).

# API Auth

### Overview

API Authentication is an essential part of the Business Manager, as it enables secure access to the DG Live APIs for your metaverse NFT store. This section covers how to obtain API credentials and use them to authenticate API calls.

### How to obtain API credentials

1. Click on the **API Auth** tab in the Business Manager dashboard.
2. If you haven't already generated API credentials, click on the **Generate API Key** button.
3. Your API Key and Secret will be displayed. Make sure to save these credentials securely, as they will be required to authenticate your API calls.

<figure><img src="https://1079496934-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FS5LS2toeP7Xkb1Vtd6fh%2Fuploads%2FJ2lt1Nt6KtMuo2nZRaLL%2FScreen%20Shot%202023-03-12%20at%2012.48.23.png?alt=media&amp;token=e4543e02-db92-4458-beac-923efb5ac432" alt=""><figcaption></figcaption></figure>

This options takes you to the API authorization screen as seen in the above image.

Using this interface you can simply create new API Keys. Several dashboard endpoints require you to have a valid API Key.&#x20;

You may find keys automatically created by the system.&#x20;

### How to use API credentials

When making API calls to DG Live APIs, include your API Key and Secret in the request headers or query parameters as required by the specific API documentation. This will ensure your API calls are securely authenticated and authorized.

### <mark style="color:red;">Warning</mark>

Do **not** share your TOKEN keys with anyone outside of your organization. Doing so may have serious security consequences. &#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dg-market.gitbook.io/dg-live/business-manager/api-auth.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.