Skip to main content
Technical Preview

Overview

Client-mode REST API connector for the QAD Redzone public API v2: OAuth token and locations plus runs and shifts and maintenance actions and data sheets and event polling. BASE_ADDRESS defaults to https://api.rz-ops.com. Topics use mes/redzone/<object>/<verb>.

Authentication

OAuth 2.0 client credentials. POST /public/v2/oauth/token with {“client_id”,“client_secret”} (JSON) returns an access token; send it as Authorization: Bearer {value.json.access_token}. Client ID and secret are issued by Redzone to the customer organization. Runs, shifts, data sheets and problem types need the enterprise-integration entitlement; maintenance actions also need reliability-integration (x-entitlements in the OpenAPI spec).
Keep credentials in broker secrets and never retain topics that carry tokens or client secrets.

Notes

  • The Redzone OpenAPI spec (REDZONE PUBLIC API 2.0.0) is public at https://api.rz-ops.com/public/v2/openapi.json; the Developer Hub UI itself is not public.
  • API credentials (client_id / client_secret) are issued by Redzone to the customer. Nothing in the public material requires a QAD partner agreement, but endpoints tagged x-entitlements enterprise-integration (runs, shifts, data sheets, problem types) and reliability-integration (maintenance actions) need those Redzone add-ons on the customer contract.
  • OAuthToken is the only event whose body carries a credential (client_id / client_secret in the token request), the same pattern as the Box OAuthToken event. Never retain mes/redzone/oauth/# and restrict it with ACLs.
  • List endpoints require limit (1..100) and offset (>= 0) query values; pass them on every list payload.

Basic Syntax

Sources

Last modified on October 21, 2026