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

# Resumen de la API de D1

## Descripción general

Esta página proporciona una lista de verificación de los endpoints de la API D1 que normalmente se requieren para integrar 3DS.

{% 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 de D1 llama a su backend de emisor.
  {% endhint %}

## APIs requeridas

<table><thead><tr><th width="246">API</th><th width="177.5999755859375">Entrada/Salida</th><th>Descripción</th></tr></thead><tbody><tr><td><a href="/central-issuance/es/integrar-la-api-de-d1/referencia-de-la-api-de-d1/api-entrante-a-d1/api-oauth2.md#post-oauth2-token">Obtener token de autorización</a></td><td>Emisor -> Thales D1</td><td>Obtener un token de acceso OAuth 2.0 para llamar al backend de D1.</td></tr><tr><td><a href="/central-issuance/es/integrar-la-api-de-d1/referencia-de-la-api-de-d1/api-entrante-a-d1/api-de-pedido-de-tarjeta.md#post-issuers-issuerid-physicalcards-cardid-operations-production">Solicitar tarjeta</a></td><td>Emisor -> Thales D1</td><td>Solicitar una tarjeta física</td></tr><tr><td><a href="/central-issuance/es/integrar-la-api-de-d1/referencia-de-la-api-de-d1/api-entrante-a-d1/api-de-pedido-de-tarjetas.md#post-issuers-issuerid-physicalcards-batch">Solicitar tarjetas</a></td><td>Emisor -> Thales D1</td><td>Solicitar varias tarjetas físicas</td></tr></tbody></table>

## APIs opcionales

<table><thead><tr><th width="252.79998779296875">API</th><th width="170.5999755859375">Entrada/Salida</th><th>Descripción</th></tr></thead><tbody><tr><td><a href="/central-issuance/es/integrar-la-api-de-d1/referencia-de-la-api-de-d1/api-saliente-desde-d1/api-de-tarjeta.md#post-notifications-d1-v2-issuers-issuerid-cards">Notificaciones del estado del pedido de la tarjeta</a></td><td>Emisor &#x3C;- Thales D1</td><td>Recibir el estado del pedido de la tarjeta en tiempo real</td></tr><tr><td><a href="/central-issuance/es/integrar-la-api-de-d1/referencia-de-la-api-de-d1/api-entrante-a-d1/api-de-pedido-de-tarjeta.md#get-issuers-issuerid-physicalcards-cardid-productionstatus">Obtener el estado del pedido de la tarjeta</a></td><td>Emisor -> Thales D1</td><td>Obtener el estado de un pedido de tarjeta</td></tr><tr><td><a href="/central-issuance/es/integrar-la-api-de-d1/referencia-de-la-api-de-d1/api-entrante-a-d1/api-de-extraccion-y-cambio.md#post-issuers-issuerid-physicalcards-cardid-operations-updateorder">Retirar y cambiar</a></td><td>Emisor -> Thales D1</td><td>Retirar una tarjeta y solicitar aplicar un cambio</td></tr><tr><td><a href="/central-issuance/es/integrar-la-api-de-d1/referencia-de-la-api-de-d1/api-entrante-a-d1/api-del-centro-de-seguimiento.md#post-issuers-issuerid-physicalcards-cardid-track">Rastrear tarjeta</a></td><td>Emisor -> Thales D1</td><td>Solicitar el seguimiento del envío de una tarjeta</td></tr></tbody></table>


---

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