Skip to content

Flair API Overview

BOTH

Flair Classic and Flair 7 include an extensive TCP network API that allows external computers to control Flair over a standard Ethernet connection. This enables custom integrations, show control systems, and multi-robot orchestration beyond what the standard Flair UI provides.

What the API Provides

Flair's network API exposes a large command set covering:

  • Run, stop, and browse moves
  • Step through frames (single-frame control for stop motion workflows)
  • Query rig status and position
  • Synchronise multiple Flair systems in single-step mode

While writing a full custom controller is a technical undertaking, MRMC provides ready-made controllers that use the API for common workflows.

Enabling the API

Flair Classic

The following lines must be present in flair.ini:

*Api:            TCP
*ApiPort:        53025
*ApiAutoAccept:  True

These are the same settings used for Dragonframe connectivity. See Dragonframe Integration for network setup details.

Flair 7

Flair 7 uses a different default port. Check flair7.ini in the FlairClassic folder and confirm:

*ApiPort:        65500

Port mismatch after update

When updating Flair 7 from an early beta, the port may not update automatically and remains at the old value. If the Flair 7 interface does not come up correctly after an update, check flair7.ini and manually set *ApiPort: 65500.

"When updating Flair 7 from a relatively early beta to a more recent one, please check flair7.ini in the FlairClassic folder and make sure that the APIPort is set to 65500." — Gordon Eschke (MRMC)

Multi Flair API Controller

The Multi Flair API (also called Quad API Controller) is an MRMC-provided utility that connects to up to 4 running Flair systems simultaneously. It allows you to:

  • Run moves on all connected rigs with a single command
  • Step through single-frame programs in sync across all rigs
  • Browse all rigs together in sync

Connecting the Multi Flair API

  1. Ensure all Flair instances have the API enabled (see above) and are on the same network.
  2. Launch the Multi Flair API utility on a separate PC (or the same PC as one of the Flair instances).
  3. In the utility, enter the IP address and port of each Flair system.
  4. Connect — each Flair system should show as detected.
  5. Use the utility's Run/Stop/Browse controls to operate all connected rigs together.

IP address tip

If the utility can detect one Flair but not another, check that both PCs are on the same subnet. Using the Windows computer name instead of an IP address can help avoid subnet issues.

Not frame-accurate in continuous run

The Multi Flair API synchronises rigs over the network, which is not under INtime real-time control. Continuous move sync is approximate — network timing jitter will cause small offsets between rigs. For frame-accurate synchronisation of continuous moves, use hardware trigger cables (see Multi-Robot Trigger Offset Calibration). Single-step (stop motion) sync is reliable.

Obtaining the API Documentation

The full API command reference is not publicly available online. To obtain it:

  • Email support@mrmoco.com and request the API documentation.

"Not online, but contact MRMC for the details." — @simon
"Please email support@mrmoco.com and request it." — @gordon_admin

Note: MRMC entered liquidation in May 2026. Contact the Flair Community WhatsApp group for current availability of API documentation.

Use Cases

  • Custom show control: integrate Flair into a wider show control system (e.g. triggered by a media server, timecode system, or custom operator interface).
  • Multi-robot single-step: run two or more rigs through a stop motion sequence with a single button press.
  • Automation: script move start/stop for unattended or repeating shoots.
  • Monitoring: query rig state and position for display or logging.

Source: Flair API Control — talk.mrmoco.com