Reelwire

Raw data in, published posts out. An event arrives from a feed or from your own systems, Reelwire draws it into a short video with your brand on it, and posts it to the channels you have connected.

What Reelwire does, in one paragraph

Something happens: a price moves, a release ships, a council meets, an offer starts. It arrives from a feed Reelwire carries, from your own systems over the API, or from a post written by hand in a post list. A template drawn by a designer is filled with it, wearing your brand, in every aspect ratio and every language you publish in. Then it goes out, to the channels you have connected, at the time you chose, after a person has cleared it where you asked for that.

Where to start

If you are pointing an assistant at it, the AI assistants chapter has the configuration, the fifty-six tools and what no key may ever do.

If you are writing against the API, start at Authentication and then Sending events. The whole route list is generated from the running server, so it says what Reelwire actually serves rather than what somebody remembered to write down.

If you have Reelwire open, the Dashboard chapter follows the same order you will meet the screens in: brands, then channels, then one of the three ways content arrives.

The words this documentation uses

Word	What it means here
Brand	What a clip wears: names, colours, type, logo, and the legal line at the bottom.
Channel	One place posts go: one platform account, one language, wearing one brand.
Template	The composition a clip is drawn through, made by a designer and filled by machine.
Stream	Where your own systems send events, rendered through one template.
Feed	Something Reelwire carries and you subscribe a channel to.
Post list	Posts you write by hand, each going out at its own time.
Clip	One rendered video. A post to three channels in three languages is three clips.