> For the complete documentation index, see [llms.txt](https://placapi.gitbook.io/placapi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://placapi.gitbook.io/placapi-docs/vehiculo-runt/apto-para-traspaso.md).

# Apto para traspaso

`POST https://placapi.com/api/apto-traspaso`

Semáforo SÍ/NO de si un vehículo está apto para traspaso, derivado del RUNT: sin gravámenes, prendas, limitaciones a la propiedad ni garantías, y con el registro activo. Devuelve el flag y la lista de bloqueos concretos en texto listo para mostrar. `status` es ok si está apto, danger si el bloqueo es un gravamen/prenda/limitación y warn si solo el estado no es ACTIVO. Costo: 1 crédito por consulta con datos.

## Parámetros

| Campo       | Tipo    | Obligatorio | Detalle                                                                                                                                                                                                                                                                       |
| ----------- | ------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `placa`     | string  | Sí          | Placa del vehículo. 5 a 7 caracteres alfanuméricos: cubre AAA000, AAA00A y los formatos menos comunes (AAA00, AAAA00). Los guiones y espacios se ignoran.                                                                                                                     |
| `docType`   | string  | Sí          | Tipo de documento del propietario (CC, CE, NIT, PA, TI, CD, PPT, RC). Se aceptan alias comunes: PAS y PASAPORTE se normalizan a PA, y P.P.T. y P.P. —como lo abrevia la tarjeta de propiedad— se normalizan a PPT. Valores: `CC`, `CE`, `NIT`, `PA`, `TI`, `CD`, `PPT`, `RC`. |
| `docNumber` | string  | Sí          | Número de documento del propietario. Alias aceptado: `doc`.                                                                                                                                                                                                                   |
| `refresh`   | boolean | No          | Ignora la caché y vuelve a consultar la fuente oficial. Ojo: una consulta refrescada con datos siempre cobra (el hit de caché no).                                                                                                                                            |

## Ejemplo

```bash
curl -X POST 'https://placapi.com/api/apto-traspaso' \
  -H 'x-api-key: pk_live_TU_CLAVE' \
  -H 'content-type: application/json' \
  -d '{"placa": "...", "docType": "...", "docNumber": "..."}'
```

El esquema completo de la respuesta está en el [OpenAPI 3.1](https://placapi.com/openapi.json) y en la [referencia interactiva](https://placapi.github.io/reference.html).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://placapi.gitbook.io/placapi-docs/vehiculo-runt/apto-para-traspaso.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.