Overview
Client-mode REST API connectors for the Canary Historian: browse nodes and tags, read last values, raw history and aggregates, poll live data, annotations and events through the Views Read API, and write MQTT values into Canary through the Store and Forward Write API session (getSessionToken, storeData, keepAlive). This is one of the templates in the Canary Historian REST API app (canary-historian). Deploy it alongside the other connectors of that app when they depend on each other (for example a token connector plus an API connector).
Auth
- token: Identity API token as apiToken inside the JSON body (payload field body); sessionToken / liveDataToken / userToken for session, live data and Windows-account calls
- windows: Read API GetUserToken over https with username/password of a Windows account mapped to a Canary user -> userToken (5 min idle expiry). Not available on the v24+ Write API.
- secret: [“CANARY_API_TOKEN”]
- unauthenticated: [“GetVersion”]
- note: No Authorization header is sent; the Read API would also accept ‘Authorization: Bearer <apiToken>’ but the Write API documents only the body field, so both connectors use the body for consistency. Canary services typically use a self-signed certificate; the broker host must trust it.
Template parameters
BASE_ADDRESS default: https://YOUR_CANARY_HOST:55293.
Events
Deploy
Get the template card (JSON withtemplate and metadata) from the broker, then deploy the connector:
BASE_ADDRESS already filled in:
-addConnector (do not include ADD METADATA).
Usage example
CallGetVersion by publishing a JSON payload to its request topic, and read the reply on the response topic:

