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

# API credentials

Accessing features using the Nexthink APIs gives you the flexibility to create integrations from external third-party tools. Using APIs helps remove complexity, as IT teams do not have to access multiple consoles to carry out their work. API credentials provide authentication based on the OAuth client credentials, which you can manage using the Nexthink web interface.

## Accessing API credentials

To set up an integration with a Nexthink API, you must first create a set of API credentials for your instance that the external application or service must use to access the API and send requests.

Nexthink public API relies on OAuth 2.0. It comprises a Client Secret and Client ID, which the system uses to generate an access token to call an application or service.

To set up new credentials for your application:

1. Log in to the Nexthink web interface.
2. Select **Administration** from the main menu.
3. Click on **API credentials** in the navigation panel from the Account Management section.

<figure><img src="https://2357343894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJJ2qSHrtIyc9j4mVppGN%2Fuploads%2FLPRgLr0F3ETo8OnjJLo3%2Fimage.png?alt=media&amp;token=a3cbdc33-422b-49ad-93c3-2eb8c77827bf" alt=""><figcaption></figcaption></figure>

## Creating API credentials

Click on the **New OAuth client credentials** button located in the top-right of the API credentials page.

<figure><img src="https://2357343894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJJ2qSHrtIyc9j4mVppGN%2Fuploads%2FJ6f8tGpo7C3eHKsb7IGg%2Fimage.png?alt=media&amp;token=1e0dae1c-a7c3-4c03-80d4-9c97db388c27" alt=""><figcaption></figcaption></figure>

* **Name**: provide a meaningful name for the credential. Nexthink recommends using the name of the application you are configuring to call the API.
* **Description**: enter a description to inform users what applications and services use the credentials and why.
* **Permissions**: select the features you want to enable the permissions for. Some permissions are related to features that may not be available to you, for example, features in technical preview or those not included in your license.
  * **NQL API**: Select the checkbox to send API calls to extract data.
  * **Campaigns API**: Select the checkbox to send API calls to trigger campaigns.
  * **Workflows API**: Select the checkbox to send API calls to trigger and query workflows.
  * **Enrichment API**: Select the checkbox to send API calls to operate the enrichment feature.
  * **Remote Actions API**: Select the checkbox to send API calls to trigger and query remote actions.
  * **Data management**: Select the checkbox to send API calls to manage devices.
  * **Spark API**: Select the checkbox to send API calls to transfer a live conversation to Spark.
  * **Hypervisor API:** Select the checkbox to send API calls to report hypervisor monitoring data. Use this in conjunction with [Nexthink vSphere Connector](https://docs.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/inbound-connectors/connector-for-vmware-vsphere-hypervisor).
* Click on **Save and generate credentials** to generate the credentials. A new modal appears with the OAuth client credentials.

<figure><img src="https://2357343894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJJ2qSHrtIyc9j4mVppGN%2Fuploads%2F5tE2WkUXQSbgiTVLWWtf%2Fimage.png?alt=media&amp;token=c18ea96a-8e77-404a-831b-7f58eeb49c8f" alt=""><figcaption></figcaption></figure>

For security reasons, the credentials appear only once. Copy and save them securely, as you cannot access them beyond this point.

* Click on the **Copy** button for **Client ID** and **Secret key,** then paste the information into the secure vault authorized by your organization.


---

# 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://docs.nexthink.com/api/readme.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.