> For the complete documentation index, see [llms.txt](https://guia.fenicio.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guia.fenicio.help/developers/integracion-de-comercios/servicios/consulta-de-etiquetas-de-cliente.md).

# Consulta de etiquetas de cliente

Este servicio permite a Fenicio consultar las etiquetas asociadas a un cliente, con el objetivo de configurar y aplicar promociones específicas según el tipo de usuario.

| Método | URL                                 |
| ------ | ----------------------------------- |
| POST   | `https://{ApiURL}/CommerceERP/Tags` |

### Request

El *request* enviado por Fenicio será un objeto [**Comprador**](/developers/referencia/modelos-de-datos/integraciones.md#comprador).

#### Ejemplo

```json
{
  "_idSolicitud": "200325120000-FNSHPUY-3c7621ed5a707177c1421cce79338668",
  "id": 123,
  "codigo": null,
  "email": "mail@dominio.com",
  "nombre": "Juan",
  "apellido": "Pérez",
  "telefono": "+59899123456",
  "genero": "M",
  "documento": {
    "numero": "41234568",
    "pais": "UY",
    "tipo": "DOCUMENTO_IDENTIDAD"
  }
}
```

> **Nota:** De los datos enviados, Fenicio únicamente puede asegurar que el correo electrónico pertenece al usuario en cuestión.

### Response

La respuesta deberá indicar el resultado de la operación y, en caso exitoso, devolver las etiquetas asociadas al cliente.

#### Caso exitoso

```json
{
  "status": "OK",
  "mensaje": null,
  "data": {
    "tags": [
      "SOCIO_VIP",
      "CLIENTE_FRECUENTE"
    ]
  }
}
```

### Modelos de datos

#### Data

| Clave  | Tipo           | Descripción                                                           |
| ------ | -------------- | --------------------------------------------------------------------- |
| `tags` | Array\[String] | Listado de etiquetas asignadas al usuario en el sistema del comercio. |


---

# 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://guia.fenicio.help/developers/integracion-de-comercios/servicios/consulta-de-etiquetas-de-cliente.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.