> 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 Vista general de la API COM de GeoDin: puntos de entrada de automatización para scripting e integración. 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.geodin.com/geodin-desktop/es/integraciones-y-complementos/overview-1.md?ask=&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.