Home
Runtimes
Descriptions of Link runtime services.
REST API
The REST Runtme provides a REST API used to run maps and flows that have been deployed.
V2 REST API
The V2 API allows packages built in the HCL Link web UI to be deployed to a runtme server.
V2 map and deployment APIs
The deployment endpoints provide ways to manage packages depoyed to the REST Runtime.

Runtimes
Descriptions of Link runtime services.
- REST API
  The REST Runtme provides a REST API used to run maps and flows that have been deployed.
  - V2 REST API
    The V2 API allows packages built in the HCL Link web UI to be deployed to a runtme server.
    - V2 map and deployment APIs
      The deployment endpoints provide ways to manage packages depoyed to the REST Runtime.
    - V2 map and flow run APIs
      The map and flow run endpoints allow directly invokable maps and flows to be run.
    - V2 map and flow instance API
      The instance endpoints are used to get information about an asynchronous map or flow run.
  - V1 REST API
    The V1 API has two different modes it can use to run maps. It can run maps directly, or it can run cataloged maps.
- Flow Command Server
  Deploy a flow from the HCL Link to the local filesystem using Execution flow server definition.
- Map Command Server
  To use the Map Command Server to execute a map, you will prepare the maps for execution.
- SDK
  The LNK programming interface includes language-specific methods and objects that provide common functionality across multiple environments.

V2 map and deployment APIs

The deployment endpoints provide ways to manage packages depoyed to the REST Runtime.

These APIs can list packages on the server, get detailed informatin about a package, delete a package, or deploy a new package.

The POST /v2/packages endpoint allows a package contained in a SQLite file to be deployed. The SQLite files for packages are built using the HCL Link web UI. In typical usage, this API is not called directly. It is called automatically when performing a deployment through the UI.