Skip to main content
Technical Preview

Overview

Client-mode REST API connector for Fracttal One CMMS: create work requests from alarms, turn them into pending tasks and work orders, update work order status and notes or cancel them, read and update assets, create meters and push meter readings, with OAuth 2.0 client credentials. This is one of the templates in the Fracttal One REST API app (fracttal-one). Deploy it alongside the other connectors of that app when they depend on each other (for example a token connector plus an API connector).
Not yet verified against the live vendor API: No Fracttal One account or OAuth consumer on the factory box (no FRACTTAL_* variables); only static, mock, negative-control and fake-credential public probes ran.

Auth

OAuth 2.0 client credentials (queue hint ‘API key + secret’ refers to the older Hawk scheme, which needs a per-request MAC and is not used). GetToken / RefreshToken: Basic base64(key:secret) + form body to https://one.fracttal.com/oauth/token; tokens last 7200 s. API events: Authorization: Bearer <access_token> from payload. Every event also sends User-Agent: Coreflux-Broker. Auth headers used by the template: Authorization: Bearer {value.json.access_token}.

Template parameters

BASE_ADDRESS default: https://app.fracttal.com.

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 ListAssets by publishing a JSON payload to its request topic, and read the reply on the response topic:
Last modified on October 21, 2026