> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/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/platform/ja/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/nexthink-api.md).
# Nexthink API
NexthinkのAPIを使用して機能にアクセスすることで、外部のサードパーティツールとの統合を自由に行うことができます。 APIを使用することで、複数のコンソールにアクセスすることなく作業を行うことができ、ITチームの複雑さを軽減します。
### 認証方法
Nexthinkのウェブインターフェースを構成し、OAuthというアクセス委譲のためのオープンスタンダードを使用して様々なAPIへのアクセスを許可できます。詳細については、[Nexthink Developer Portal](https://docs.nexthink.com/api)のドキュメントを参照してください。
[Nexthink サポート](https://support.nexthink.com/)に問い合わせて、詳細情報を入手してください。
### Nexthink API の一覧
* [Enrichment API](https://docs.nexthink.com/api/enrichment)
* [Campaign API](https://docs.nexthink.com/api/campaigns)
* [Remote Actions API](https://docs.nexthink.com/api/remote-actions)
* [NQL API](https://docs.nexthink.com/api/nql)
* [Spark API](https://docs.nexthink.com/api/spark)
* [Workflows API](https://docs.nexthink.com/api/workflows)
[Nexthink サポート](https://support.nexthink.com/)に問い合わせて、詳細情報を入手してください。
---
# 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/platform/ja/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/nexthink-api.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 `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.