> 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/wallet-enablement/es/referencia-de-api/directrices.md).

# Directrices

## Consideraciones de desarrollo

Los siguientes cambios se consideran compatibles con versiones anteriores:

* Agregar una nueva solicitud de API
* Agregar un nuevo parámetro opcional a una API existente (solicitud/respuesta)
  * Este parámetro podría agregarse como cuerpo, parámetro HTTP o encabezado HTTP
* Agregar un nuevo valor en una enumeración
* Hacer opcionales los parámetros obligatorios
* Ignorar cualquier campo/valor desconocido recibido como parte de la solicitud/respuesta de la API

## Correlación de las API

Todas las llamadas a la API relacionadas con el mismo caso de uso deberán usar el mismo **x-request-id (TSP API v1) o x-correlation-id (TSP API v2)** valor.

*Nota para los TSP que también implementan la* [***API de Issuer Gateway***](https://tsh-issuer-gateway.docs.stoplight.io/)*:*\
*El valor proporcionado en el **x-correlation-id** encabezado HTTP se mantiene en todas las llamadas a la API para el flujo de digitalización.*\
*Lo mismo aplica para los flujos del ciclo de vida.*


---

# 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/wallet-enablement/es/referencia-de-api/directrices.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.