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

# Verkada Command API

Verkada APIが他のアプリケーションにVerkadaとのインターフェースを提供する仕組みを学ぶ

この [Verkada アプリケーション・プログラミング・インターフェース (API)](https://apidocs.verkada.com/reference/introduction) Commandプラットフォームおよび Verkada デバイスとプログラムで連携できます。これにより、データの抽出、タスクの自動化、他の製品との安全かつ拡張性の高い統合が可能になります。

この API は **RE**表現の **S**状態 **T**ransfer (REST) ベースで、JavaScript Object Notation (JSON) でエンコードされた応答を返し、標準の Hypertext Transfer Protocol Secure (HTTP) 応答コードを使用します。

***

{% hint style="info" %}
**実際の動作をご覧になりますか？** こちらを [ビデオチュートリアル](https://www.youtube.com/watch?v=pfpREEcj11M).
{% endhint %}


---

# 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://help.verkada.com/command/ja/ganaizshon/verkada-command-api.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.