Link provides several ways to connect external applications, trading partners, and AI assistants to its data and functionality. You can use the built-in APIs, extend Link with custom HTTP endpoints, or expose selected operations as tools through an MCP server.
This section helps you choose the appropriate integration approach and understand how to authenticate and access it.
-
API Authentication — Understand the supported authentication methods and how user roles and permissions determine access.
-
Link API — Explore the built-in interfaces for message exchange, document and configuration data, tracking, and configuration imports.
-
HTTP Handlers — Learn how regular and Advanced HTTP Handlers extend Link with custom endpoints and business logic.
Link also supports MCP servers (preview), which expose selected functionality as tools that MCP-compatible clients can discover and invoke. See the MCP development guide for implementation and configuration details.
For a standard integration, start with the built-in APIs. Use HTTP Handlers when you need a custom HTTP interface, or an MCP server when you want to make functionality available through the Model Context Protocol.