> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/wallet-enablement/ja/apirifarensu/gaidorain.md).

# ガイドライン

## 開発上の考慮事項

以下の変更は後方互換ありと見なされます:

* 新しい API リクエストの追加
* 既存の API に新しい任意パラメータを追加する（リクエスト／レスポンス）
  * このパラメータは body、HTTP パラメータ、または HTTP ヘッダーとして追加できます
* enum に新しい値を追加する
* 必須パラメータを任意にする
* API リクエスト／レスポンスの一部として受信した不明なフィールド／値は無視する

## API の相関付け

同じユースケースに関連するすべての API 呼び出しは、同じ **x-request-id（TSP API v1）または x-correlation-id（TSP API v2）** 値を使用する。

*また、次のものを実装する TSP 向けの注意:* [***イシュア Gateway API***](https://tsh-issuer-gateway.docs.stoplight.io/)*:*\
*に提供される値は **x-correlation-id** HTTP ヘッダーは、デジタライゼーションフローのすべての API 呼び出しにわたって保持されます。*\
*ライフサイクルフローにも同じことが当てはまります。*


---

# 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.payments.thalescloud.io/wallet-enablement/ja/apirifarensu/gaidorain.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.