> 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/pin-management/ja/d1-sdkwosuru/no.md).

# 統合の概要

D1 SDK の API を呼び出すには、次のセットアップが必要です：

1. D1 SDK バイナリ統合（ [Android ](/pin-management/ja/d1-sdkwosuru/hajimeni/she-ding/1-bainari/android.md)および [iOS](/pin-management/ja/d1-sdkwosuru/hajimeni/she-ding/1-bainari/ios.md).
2. [初期設定](/pin-management/ja/d1-sdkwosuru/hajimeni/she-ding/2-onbdingu/chu-qi-she-ding.md).
3. の初期化 [Android ](/pin-management/ja/d1-sdkwosuru/hajimeni/she-ding/3.-chu-qi-hua/androidno.md)および [iOS](/pin-management/ja/d1-sdkwosuru/hajimeni/she-ding/3.-chu-qi-hua/iosno.md).
4. [プッシュ通知](/pin-management/ja/d1-sdkwosuru/hajimeni/she-ding/4-pusshu/pusshuno.md) 構成。
5. [SDK ログイン](/pin-management/ja/d1-sdkwosuru/hajimeni/she-ding/5.-ren-zheng/sdkroguin.md).

### 参照実装

D1 SDK 統合を支援するために、Thales はサンプルアプリの形式で参照実装を提供しています。参照： [参照実装](/pin-management/ja/d1-sdkwosuru/hajimeni/rifarensu.md).

### API リファレンス

D1 SDK の API は以下のリンクで参照できます：

* [Android API リファレンス](https://thalesgroup.github.io/d1sdk-docs/d1-sdk/latest/android/)
* [iOS API リファレンス](https://thalesgroup.github.io/d1sdk-docs/d1-sdk/latest/ios/)


---

# 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/pin-management/ja/d1-sdkwosuru/no.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.