> 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/integrate-the-d1-api/d1-api-summary.md).

# D1 API summary

## Overview

This page provides a checklist of the D1 API endpoints typically required to integrate PIN Management.

{% hint style="info" %}
**Direction** indicates who calls the endpoint:

* **Inbound**: your issuer backend calls the D1 API.
* **Outbound**: the D1 backend calls your issuer backend.
  {% endhint %}

### Required APIs <a href="#required-apis" id="required-apis"></a>

| API                                                                                                                                                                                                                                                                              | Inbound/Outbound    | Description                                           |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | ----------------------------------------------------- |
| [​Get authorization token​](/pin-management/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/oauth2-api.md#post-oauth2-token)                                                                                                                                             | Issuer -> Thales D1 | Get an OAuth 2.0 access token to call the D1 backend. |
| [​Create card](/pin-management/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards) or [Register card​](/pin-management/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#put-v2-issuers-issuerid-cards-cardid) | Issuer -> Thales D1 | Create or register a card in the D1 backend.          |
| [​Renew card​](/pin-management/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-renew)                                                                                                                       | Issuer -> Thales D1 | Renew a card.                                         |
| [​Replace card​](/pin-management/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-replace)                                                                                                                   | Issuer -> Thales D1 | Replace a card.                                       |
| [​Delete card​](/pin-management/integrate-the-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards-cardid-operations-delete)                                                                                                                     | Issuer -> Thales D1 | Delete a card from the D1 backend.                    |

### Optional APIs <a href="#optional-apis" id="optional-apis"></a>

Use the APIs below depending on which flow you enable

| API                                                                                                                                                          | Inbound/Outbound    | Description                                                                |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | -------------------------------------------------------------------------- |
| [Get authorization token](/pin-management/integrate-the-d1-api/d1-api-reference/outbound-api-from-d1/oauth2-api.md#post-oauth2-token)                        | Issuer <- Thales D1 | Get an OAuth 2.0 access token to call the Issuer backend.                  |
| [Get PIN](/pin-management/integrate-the-d1-api/d1-api-reference/outbound-api-from-d1/pin-management-api.md#get-cms-api-v1-issuers-issuerid-cards-cardid-pin) | Issuer <- Thales D1 | Retrieve the PIN from Issuer backend in order to display it on the mobile. |
| [Set PIN](/pin-management/integrate-the-d1-api/d1-api-reference/outbound-api-from-d1/pin-management-api.md#put-cms-api-v1-issuers-issuerid-cards-cardid-pin) | Issuer <- Thales D1 | Set the PIN from mobile app to the Issuer backend.                         |


---

# 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/integrate-the-d1-api/d1-api-summary.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.