> 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/implementar-la-emision-centralizada/seguimiento-de-pedidos-de-tarjetas/seguimiento-de-pedidos-bajo-demanda.md).

# Seguimiento de pedidos bajo demanda

Su backend emisor puede consultar el estado actual de producción y envío en cualquier momento.

Esto es útil para conciliar el estado después de notificaciones perdidas.

### APIs requeridas

<table><thead><tr><th width="190.39996337890625">API</th><th width="176">Entrante/Saliente</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-de-pedido-de-tarjeta.md#get-issuers-issuerid-physicalcards-cardid-productionstatus">Obtener estado del pedido de tarjeta</a></td><td>Emisor -> Thales D1</td><td>Recuperar el estado más reciente de un pedido de tarjeta física.</td></tr></tbody></table>

### Entradas de la API

Entradas requeridas de la API D1:

* `issuerId`: Identificador único del emisor.
* `cardId`: Identificador único de la tarjeta.

### Respuesta

La respuesta utiliza el mismo `objeto` de operaciones que las notificaciones.

Ver [Seguimiento de pedidos de tarjetas](/central-issuance/es/implementar-la-emision-centralizada/seguimiento-de-pedidos-de-tarjetas.md) para las definiciones de los campos.

#### Ejemplo

{% tabs %}
{% tab title="Solicitud" %}
{% hint style="info" %}
Reemplace los marcadores de posición con los valores de su entorno. Consulte la referencia de la API para la ruta exacta del endpoint y el esquema de autenticación.
{% endhint %}

```bash
curl -X GET \
  "https://{base_url}/issuers/{issuerId}/physicalcards/{cardId}/productionstatus" \
  -H "Authorization: Bearer {access_token}" \
  -H "Accept: application/json"
```

{% endtab %}
{% endtabs %}


---

# 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/implementar-la-emision-centralizada/seguimiento-de-pedidos-de-tarjetas/seguimiento-de-pedidos-bajo-demanda.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.