Skip to main content
Technical Preview

Overview

Client-mode REST API connector for Epicor Kinetic OData v2 (Jobs, Labor, Parts, Inventory). BASE_ADDRESS defaults to https://YOUR_SERVER/YOUR_INSTANCE/api/v2/odata/YOUR_COMPANY. Auth: Basic or API key + Bearer (Epicor Identity). Pass secrets only at runtime via MQTT JSON placeholders or Hub GET SECRET — never commit real credentials.

Auth

Basic or API key + Bearer (Epicor Identity). Prefer Hub secrets / GET SECRET. Never hard-code tokens into the .lot.

Basic Syntax

MQTT topics

Request topics under integrations/epicor-kinetic/request/...; responses on integrations/epicor-kinetic/response/....

Template reference

Generated from the shipped broker template epicor-kinetic (-routeCode EPICOR_KINETIC). It lists every event the template defines.

Auth

Basic or API key + Bearer (Epicor Identity) Auth headers used by the template: Authorization: Bearer {value.json.access_token}, x-api-key: {value.json.api_key}.

Template parameters

BASE_ADDRESS default: https://YOUR_SERVER/YOUR_INSTANCE/api/v2/odata/YOUR_COMPANY.

Events

Deploy

Get the template card (JSON with template and metadata) from the broker, then deploy the connector:
The deployable connector from the REST API app, with BASE_ADDRESS already filled in:
Deploy it with -addRoute (do not include ADD METADATA).

Usage example

Call Listjobs by publishing a JSON payload to its request topic, and read the reply on the response topic:
Last modified on October 21, 2026