> 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-consulta-and-canje-de-puntos/registro-de-cliente.md).

# Registro de cliente

Fenicio envía (por única vez) la información del cliente para su registro en el sistema del comercio y lo vincula a través del código que obtenga del mismo.

| Método     | URL                               |
| ---------- | --------------------------------- |
| **`POST`** | https\://{ApiURL}/registrocliente |

## Request

### Usuario

| Clave           | Tipo                                                                                                                 | Descripción                                            |
| --------------- | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ |
| **`email`**     | String(255)                                                                                                          | Email del usuario                                      |
| **`nombre`**    | String(255)                                                                                                          | Nombre del usuario                                     |
| **`apellido`**  | String(255) \| null                                                                                                  | Apellido del usuario                                   |
| **`telefono`**  | String(255)                                                                                                          | <p>Teléfono del usuario. </p><p>Ejemplo: 099123456</p> |
| **`documento`** | [**Documento**](https://guia.fenicio.help/developers/referencia/modelos-de-datos/integraciones.md#documento) \| null | Datos del documento del usuario                        |

### Documento

| Clave        | Tipo       | Descripción                                                             |
| ------------ | ---------- | ----------------------------------------------------------------------- |
| **`numero`** | String(32) | Número de documento                                                     |
| **`tipo`**   | String     | Tipo de documento. Valores posibles: `PASAPORTE`, `DOCUMENTO_IDENTIDAD` |

### Ejemplo

```json
{
 "_idSolicitud": "200325120000-FNSHPUY-3c7621ed5a707177c1421cce79338668",
 "email": "mail@dominio.com",
 "nombre": "Juan",
 "apellido": "Pérez",
 "telefono": "099123456",
 "documento": {
 "numero": "41234568",
 "tipo": "DOCUMENTO_IDENTIDAD"
 }
}
```

## Response

### Caso de exitoso

```json
{
 "status": "OK",
 "mensaje": "Usuario registrado.",
 "_idSolicitud": "200325120000-FNSHPUY-3c7621ed5a707177c1421cce79338668",
 "data": {
 "codigo": "abc12345"
 }
}
```

### Caso de error

```json
{
 "status": "ERROR",
 "mensaje": "El usuario no se ha registrado.",
 "_idSolicitud": "200325120000-FNSHPUY-3c7621ed5a707177c1421cce79338668",
}
```

En el campo 'mensaje', pueden retornar los diferentes errores que se presenten durante el\
intento de registrar un usuario. En caso de éxito, el mensaje podría ser 'Usuario registrado'. En\
caso de error, el mensaje deberá describir la causa del fallo, como por ejemplo 'El usuario no se\
ha registrado', o bien detallar el motivo específico del error.


---

# 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-consulta-and-canje-de-puntos/registro-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.
