Glink offers a wide range of APIs (Application Programming Interfaces).
Glink has of course support for the traditional APIs, such as Bull-UVTI and IBM-HLLAPI and EHLLAPI. Additionally Glink offers an OLE automation server interface to OLE automation controllers, such as Microsoft Office applications, including Word and Excel, that support the Visual Basic Application language (VBA). For integration with advanced applications Glink offers both COM+ and .NET interfaces.
OLE automation server
The Glink.Auto object makes Glink into an OLE automation server. All Microsoft Office applications, including Word and Excel, that support the Visual Basic Application language (VBA) are able to act as OLE automation controllers and drive Glink as an OLE automation server. Your own VBScripts or JScripts launched from your applications or desktop can also use Glink.Auto. Note that Glink itself can launch your VBScripts or JScripts, and passes Glink.Auto to the ScriptControl, allowing your script to interact with the Glink session that launched it.
COM+ and .NET
Glink Professional Edition provides a COM+ component, Glink.GlinkAPI for development of workstation applications. The Enterprise Edition includes a Glink API for server-side development of .NET applications. All visual development tools (Visual Basic, Visual C, Visual Java) recognize the Glink COM+ and .NET component, and are able to display the interface to the developer. Each legacy application screen becomes addressable as a collection of field objects, or as a string. Your developers can deliver keystrokes and can set up event handlers that will call back the client application when the given event occurs (connect, disconnect, turn, reception of a specified string or keyboard sequence).