> 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/integrations-and-plug-ins/overview-1.md). # COM API Overview of GeoDin's COM API - automation entry points for scripting and integration. GeoDin exposes a **COM API** that lets external scripts and applications automate object creation, data access, layout printing, and other GeoDin operations. The COM API is accessible from any language that supports COM automation (VBA, VBScript, PowerShell, .NET via interop, Python via `comtypes`). Typical use cases include batch report generation, programmatic data import, and integration with third-party project management tools. ## Image Server module Some COM methods belong to the **GeoDin Image Server** module rather than to the base API. The Image Server makes GeoDin data available graphically to a front-end program in an intranet or Internet environment, directly from a GeoDin database: it renders GeoDin layouts as images that the front end can display. The module is licensed with the GeoDin Server Licence, and it is exercised through the COM methods [GetImage](/integrations-and-plug-ins/overview-1/method-reference.md#getimage) and [GetPrintFile](/integrations-and-plug-ins/overview-1/method-reference.md#getprintfile). Calls to those methods fail with the "function not licensed" error when the module is not licensed. For the comprehensive reference - full syntax, all options, edge cases - see [**Method Reference**](/integrations-and-plug-ins/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/integrations-and-plug-ins/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.