> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/geodin-desktop/es/integraciones-y-complementos/overview-1.md).

# API COM

GeoDin expone una **COM API** que permite a scripts y aplicaciones externas automatizar la creación de Perforación, el acceso a datos, la impresión de Seleccionar diseño y otras Operaciones de ejecución de GeoDin.

La API de COM es accesible desde Cualquiera Idioma que admita la automatización de COM (VBA, VBScript, PowerShell, .NET mediante interop, Python mediante `comtypes`). Los casos de uso típicos Incluir la generación de Lote de Informe, Importar datos de forma programática y Usar herramientas de gestión de Proyecto de Tercero.

Para la referencia completa - sintaxis completa, todas las opciones, casos extremos - consulte [**Referencia de Método**](/geodin-desktop/es/integraciones-y-complementos/overview-1/method-reference.md).


---

# 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://docs.geodin.com/geodin-desktop/es/integraciones-y-complementos/overview-1.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.