Integrations Overview: API Keys and Flex Rental Solutions

Integrations are how your organization keeps BackOps in step with the other systems your business already runs on. Most production companies already have a rental or inventory system, a booking tool, or a script someone wrote to pull show data into a spreadsheet. Without a connection, every new job gets typed in twice and the two copies drift apart.

Why Integrations Matter

Event details change constantly: dates move, a venue changes, a status goes from hold to confirmed. When those details live in two systems, someone has to remember to update both, and the copy nobody updated becomes the one the crew reads on show day. An integration makes one system feed the other, so a change is made once.

How Integrations Work

BackOps offers two ways in. Both are set up by an organization admin in Settings.

API keys. BackOps has an open API. An API key lets a tool you control, such as a script, a reporting job, or a connector your developer builds, call that API on behalf of your organization. See API keys.

Flex Rental Solutions. If your organization runs Flex, BackOps can sync with it directly. The Flex integration has three parts:

• Event sync turns Flex elements into BackOps events and keeps the fields you map up to date. See Flex event sync.
• Contact sync brings Flex contacts in as crew and collaborators. See Flex contact sync.
• Write-back sends selected changes made in BackOps back to Flex. See Pushing changes to Flex.

flowchart LR
    F["Flex"] -->|"Event sync"| E["BackOps events"]
    F -->|"Contact sync"| C["Crew and collaborators"]
    E -->|"Push to Flex"| F
    T["Your tools"] -->|"API key"| A["BackOps API"]

Flex is the only built-in integration today. Other connections are built with the API, and BackOps builds some integrations client by client depending on how an organization works.