> 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/es/integrar-la-api-d1/resumen-de-la-api-d1.md).

# Resumen de la API D1

## Resumen

Esta página proporciona una lista de verificación de los endpoints de la API D1 típicamente requeridos para integrar la Gestión de PIN.

{% hint style="info" %}
**Dirección** indica quién llama al endpoint:

* **Entrante**: el backend de su emisor llama a la API D1.
* **Saliente**: el backend D1 llama a su backend del emisor.
  {% endhint %}

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

| API                                                                                                                                                                                                                                                                                                               | Entrante/Saliente   | Descripción                                                     |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | --------------------------------------------------------------- |
| [Obtener token de autorización](/pin-management/es/integrar-la-api-d1/referencia-de-la-api-d1/api-entrante-a-d1/api-oauth2.md#post-oauth2-token)                                                                                                                                                                  | Emisor -> Thales D1 | Obtenga un token de acceso OAuth 2.0 para llamar al backend D1. |
| [Crear tarjeta](/pin-management/es/integrar-la-api-d1/referencia-de-la-api-d1/api-entrante-a-d1/api-de-tarjetas.md#post-v2-issuers-issuerid-cards) o [Registrar tarjeta](/pin-management/es/integrar-la-api-d1/referencia-de-la-api-d1/api-entrante-a-d1/api-de-tarjetas.md#put-v2-issuers-issuerid-cards-cardid) | Emisor -> Thales D1 | Crear o registrar una tarjeta en el backend D1.                 |
| [Renovar tarjeta](/pin-management/es/integrar-la-api-d1/referencia-de-la-api-d1/api-entrante-a-d1/api-de-tarjetas.md#post-v2-issuers-issuerid-cards-cardid-operations-renew)                                                                                                                                      | Emisor -> Thales D1 | Renovar una tarjeta.                                            |
| [Reemplazar tarjeta](/pin-management/es/integrar-la-api-d1/referencia-de-la-api-d1/api-entrante-a-d1/api-de-tarjetas.md#post-v2-issuers-issuerid-cards-cardid-operations-replace)                                                                                                                                 | Emisor -> Thales D1 | Reemplazar una tarjeta.                                         |
| [Eliminar tarjeta](/pin-management/es/integrar-la-api-d1/referencia-de-la-api-d1/api-entrante-a-d1/api-de-tarjetas.md#post-v2-issuers-issuerid-cards-cardid-operations-delete)                                                                                                                                    | Emisor -> Thales D1 | Eliminar una tarjeta del backend D1.                            |

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

Utilice las APIs a continuación dependiendo del flujo que active

| API                                                                                                                                                                             | Entrante/Saliente   | Descripción                                                              |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | ------------------------------------------------------------------------ |
| [Obtener token de autorización](/pin-management/es/integrar-la-api-d1/referencia-de-la-api-d1/api-saliente-desde-d1/api-oauth2.md#post-oauth2-token)                            | Emisor <- Thales D1 | Obtenga un token de acceso OAuth 2.0 para llamar al backend del Emisor.  |
| [Obtener PIN](/pin-management/es/integrar-la-api-d1/referencia-de-la-api-d1/api-saliente-desde-d1/api-de-gestion-de-pin.md#get-cms-api-v1-issuers-issuerid-cards-cardid-pin)    | Emisor <- Thales D1 | Recuperar el PIN desde el backend del Emisor para mostrarlo en el móvil. |
| [Establecer PIN](/pin-management/es/integrar-la-api-d1/referencia-de-la-api-d1/api-saliente-desde-d1/api-de-gestion-de-pin.md#put-cms-api-v1-issuers-issuerid-cards-cardid-pin) | Emisor <- Thales D1 | Establecer el PIN desde la aplicación móvil al backend del Emisor.       |


---

# 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/es/integrar-la-api-d1/resumen-de-la-api-d1.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.