> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/jp/api-troubleshooting/api-parameters.md).

# APIパラメータ

## 要件

APIエンドポイントを利用する前に、Keeper担当者から以下の情報が必要です。

* Partner Name
* Salt

APIエンドポイントで正常なレスポンスを得るには、この情報が必要です。

{% hint style="warning" %}
Partner NameまたはSaltをお持ちでない場合は、Keeper担当者にお問い合わせください。
{% endhint %}

## APIパラメータ

Keeper Provision APIでリクエストを成功させるには、APIエンドポイントに以下のパラメータが必要です。

| パラメータ                          | 説明                                                                                                                         |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------- |
| transaction\_id (string)       | <p>Partner Transaction ID。社内管理用のカスタムID。</p><p>例: "0001", "user1"</p>                                                       |
| first\_name (string)           | 名 (ファーストネーム)                                                                                                               |
| last\_name (string) (optional) | 姓 (ラストネーム) (任意)                                                                                                            |
| email (string)                 | <p>ユーザーのメールアドレス</p><p>アカウント作成用の招待メールが送信されます</p>                                                                            |
| hash (string)                  | <p>ユーザーのメールアドレスとKeeperから提供されたSaltをSHA-256でハッシュ化して生成。<br><code>hash = SHA256.hexdigest.bytesToHex(email + salt )</code></p> |
| partner\_name (string)         | Keeper担当者から提供される Partner Name                                                                                              |


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/enterprise-guide/jp/api-troubleshooting/api-parameters.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.