Overview
A client-mode connector for a curated CMMS / EAM slice of the IBM Maximo Manage REST/JSON APIs (object structures underhttps://YOUR_MAXIMO_HOST/maximo):
BASE_ADDRESS is https://{host}/maximo (no trailing slash; endpoints already include /api/os/...). Topics use cmms/ibm-maximo-manage/<object>/<verb>.
Prefer Hub secrets for API keys and passwords. This template has not been verified against a live Maximo Manage host. Status remains blocked until an authenticated live smoke succeeds.
Basic Syntax
Parameters
Authentication
- API key (preferred for MAS 8.8+): header
apikey: <key>. Do not rely on maxauth for Manage integrations. - Basic / LDAP: configure USERNAME + PASSWORD (GET SECRET) on
REST_API_CONFIG. - Prefer Hub secrets. Never commit real credentials.
MQTT topics
Responses publish on the same topic with
/response appended.
Example payloads
List approved work orders (smoke):Notes and version quirks
- Use
lean=1so JSON bodies do not require namespaces. properties: *on writes asks Maximo to return selected fields in the create/update response.- Native HTTP PATCH may not be enabled on every install; IBM docs often show
POST+x-method-override: PATCH(+ optionalpatchtype: MERGE). Fork the Patchasset event if needed. - Meter readings via
MXAPIMETERREADINGcan requirex-method-override: SYNCon some systems; an alternate is nestedassetmeterupdates onMXAPIASSET. - Object structures must be enabled / authorized for the API user in Maximo.

