Case study

A client's story in three beats, a page each: the challenge, what was done in up to three numbered steps and the result as up to three figures counting to exactly what is sent, then the client's quote; the title and a picture on the cover: 16 to 20 seconds. In eight styles, each wearing your brand's colours, fonts, logo, presenter and background.

Template id	tpl_b89f35e4a1f4
Markets	Every market
Variants	Corporate glass, Bento grid, Broadcast news, Editorial, Swiss grid, Neo-brutalist, Soft friendly, Keynote minimal
Ready-made feeds	None

Use cases

• A client's story told as proof: what was wrong, what was done and the figures that changed.
• A project, a service or a product rollout, with up to three results counting to exactly what you send.
• The client's own words on a last page, with their name and role.

Variants

A variant is this template drawn another way, and it comes in versions: immutable builds, the newest first. A channel follows the newest version of its variant, unless it is pinned to one.

Variant	What it is	Versions	Newest
Corporate glass	Frosted glass cards over an aurora in your brand colours: calm and premium.	1	1.0.0
Bento grid	Rounded tiles in your brand colours, each moving on its own: a modern product look.	1	1.0.0
Broadcast news	A news channel in your colours: channel bug, lower third, ticker and your presenter.	1	1.0.0
Editorial	A magazine page in your paper tone and serif: masthead, hairline rules and a byline.	1	1.0.0
Swiss grid	A strict grid, large type and your brand colour as the one accent. Nothing bounces.	1	1.0.0
Neo-brutalist	Loud flat blocks in your colours with thick borders and hard shadows.	1	1.0.0
Soft friendly	Soft shapes and rounded cards in tints of your brand colour: warm and approachable.	1	1.0.0
Keynote minimal	A launch stage: one thing at a time, huge type and a light sweep in your colour.	1	1.0.0

What it accepts

Every variant takes the same content, so one document draws in any of them.

Case study: a title and a picture on the cover, then the challenge, what was done in up to three numbered steps, the result as up to three figures counting to exactly what is sent, and the client's quote. metaData is the post's title, descriptions and hashtags and is never drawn.

Field	Type	Required	Limit	What it is
clipData	group	yes		Clip data: Everything drawn: the cover, the challenge, the steps, the results, the quote, the words over each part, the note and the look.
clipData.kicker	text		up to 20 characters	Kicker: A word or two above the title on the cover, such as CASE STUDY.
clipData.title	text	yes	up to 80 characters	Title: The story in one line, as it is said: who, and what changed. The cover's heading, and the line over every part after it.
clipData.picture	image		media:// file from the media library, alt text up to 120 characters	Picture: The client, the place or the project, on the cover under the title. Left out, the title has the cover to itself.
clipData.pictureFit	enum		auto, fill, whole	Picture fit: Automatic, the default, fills the frame when a picture is close to its shape and shows it whole when filling would cut off more than a sixth of it, so no picture is cropped away. Fill the frame always crops to the frame, right for photographs; Show it whole never crops, right for logos and cut-out products.
clipData.pictureFocus	enum		centre, top, bottom, left, right	Picture focus: Which part of a picture stays in view when it fills its frame and its edges are cropped: the middle, or one side.
clipData.challengeLabel	text		up to 24 characters	Word over the challenge: Over the challenge's page, in the language of the clip, such as The challenge. Left out, the page has the title alone over it.
clipData.challenge	text	yes	up to 160 characters	The challenge: What was wrong or what was wanted before, in a sentence or two, set as large as its page holds it.
clipData.actionLabel	text		up to 24 characters	Word over the steps: Over the steps' page, such as What we did.
clipData.actions	list	yes	at least 1, up to 3	What was done: One to three steps, numbered and arriving one after another. Each adds a second and a half.
clipData.actions[]	text		up to 90 characters	Step
clipData.resultLabel	text		up to 24 characters	Word over the results: Over the results' page, such as The result.
clipData.results	list	yes	at least 1, up to 3	Results: One to three figures, each counting up to exactly the value sent, with what it measures under it.
clipData.results[]	group			Result
clipData.results[].value	number	yes		Value: The figure, exactly as it should read.
clipData.results[].prefix	text		up to 4 characters	Before the figure: A currency sign or a word before it, such as EUR.
clipData.results[].unit	text		up to 8 characters	After the figure: A unit after it, such as % or h.
clipData.results[].decimals	integer		from 0, to 3	Decimals: How many decimals it is written with. Left out, as many as the value has.
clipData.results[].label	text	yes	up to 48 characters	What it measures
clipData.quote	group			The client's quote: What the client said about it, on a last page. Left out, the story ends on the results.
clipData.quote.text	text		up to 160 characters	Quote: Their own words. The quotation marks are the language's own and added for you.
clipData.quote.name	text		up to 40 characters	Name
clipData.quote.role	text		up to 48 characters	Role: Who they are: a job and a company.
clipData.note	text		up to 70 characters	Note: Where the figures come from, at the foot of every page. Drawn exactly as written, as the template adds no word of its own.
clipData.styleWords	group			Style words: The few words some styles write into their own frame, each drawn exactly as written, in the language you write it in. A word left out is not drawn: no template adds a word of its own. The same keys in every format of the collections; each style draws only its own.
clipData.styleWords.live	text		up to 16 characters	Live marker (Broadcast news): Written beside the light in Broadcast news' channel bug, such as LIVE. Left out, the light stands alone.
clipData.styleWords.byline	text		up to 12 characters	Byline (Editorial): Written before the presenter's name in Editorial, such as By. Left out, the name stands alone.
clipData.styleWords.functionKeys	list		up to 4	Function keys (Data terminal): Data terminal's row of keys F1 to F4, one word each, in order, such as HELP, DATA, CHART and NEWS; the second is drawn held down, and a key that does not fit the row is left out. Left out, no keys are drawn.
clipData.styleWords.functionKeys[]	text		up to 12 characters	Key
clipData.styleWords.commandKey	text		up to 10 characters	Command key (Data terminal): The key at the end of Data terminal's row, in the rise colour, such as GO. Left out, none is drawn.
clipData.styleWords.realTime	text		up to 12 characters	Real-time light (Data terminal): Written beside the blinking light in Data terminal's status bar, such as RT. Left out, the light stands alone.
clipData.styleWords.messageLabel	text		up to 12 characters	Message window label (Data terminal): The tab on Data terminal's message window round the presenter, such as MSG. Left out, the window has no tab.
clipData.styleWords.pictureLabel	text		up to 12 characters	Picture panel label (Data terminal): Written in the strip along the top of Data terminal's picture panels, such as IMG. Left out, the strip stays empty.
clipData.look	group			Look: How the clip looks and moves within its style. The same switches in every format of the collections. Leave a switch out, or set it to the style's own, and the style decides.
clipData.look.theme	enum		auto, brand, light, dark, bold	Theme: The style's own choice; your brand's own colours and background; a light or dark page tinted with your brand colour; or your brand colour as the page.
clipData.look.pace	enum		auto, calm, standard, punchy	Pace: How things arrive: the style's own rhythm, calm fades, a standard rhythm, or punchy slams and cuts.
clipData.look.corners	enum		auto, square, soft, round	Corners: The shape of cards, panels and marks.
clipData.look.align	enum		auto, start, centre	Text alignment: Where the text lines up.
clipData.look.logo	enum		auto, free	Logo: The style's own: the logo on the style's plate (a card, a disc, a badge) so it reads on any page. As it is: the logo whole, with no plate, frame or crop, for a logo made to stand on the page, such as one with a transparent background. As it is, make sure your logo reads on the page of the theme you choose.
clipData.look.logoSize	enum		auto, small, large	Logo size: Standard is the style's own size. Small draws the logo a fifth smaller, with its plate. Large draws it a quarter larger wherever the style has room for it, and at the standard size where it has none.
clipData.look.hideHeader	boolean			Hide logo and title: Leaves out the line at the top of the clip: your logo, the title line and the style's decoration around them, so the content starts at the top. To leave it out of every clip, switch Logo and title line off in your brand's settings.
clipData.look.hideFooter	boolean			Hide footer line: Leaves out your footer line at the foot of the clip, with whatever the style draws only to carry it, so the content reaches further down. Your presenter and the source line stay. To leave it out of every clip, switch Footer line off in your brand's settings.
clipData.look.pattern	enum		auto, none, dots, grid, lines	Background pattern: The fine texture behind the content. The style's own keeps what the style draws there, and some styles draw none. None leaves the background plain. Dots, Grid and Diagonal lines draw that pattern faintly instead, the same in every style, in the colour of your page.
metaData	group			Meta data: Everything about the post that is never drawn in the clip: its title, its description in four lengths, one per kind of platform, and its hashtags. Reelwire adds the brand's description, link and hashtags after it. Left out, the post text is generated from the clip data.
metaData.title	text		up to 100 characters	Title: Used where the platform has a title of its own: Facebook Feed, LinkedIn, Pinterest and YouTube. Up to 100 characters, which every one of them takes.
metaData.captionTiny	text		up to 200 characters	Tiny description (Pinterest, Threads, X): Up to 200 characters. The brand's description, link and hashtags follow it within the platform's limit.
metaData.captionShort	text		up to 500 characters	Short description (Telegram, Threema, WeChat, WhatsApp): Up to 500 characters. The brand's description, link and hashtags follow it within the platform's limit.
metaData.captionMedium	text		up to 1500 characters	Medium description (Discord, Facebook Reels, Instagram, LinkedIn, Signal, Slack, TikTok): Up to 1500 characters. The brand's description, link and hashtags follow it within the platform's limit.
metaData.captionLong	text		up to 4000 characters	Long description (Facebook Feed, YouTube): Up to 4000 characters. The brand's description, link and hashtags follow it within the platform's limit.
metaData.hashtags	list		up to 15	Hashtags: Written without the #. Up to 15, which every platform takes.
metaData.hashtags[]	text		up to 60 characters	Hashtag

locales carries other languages: under each language code, the parts of clipData and metaData that differ, laid over the default, so a language with no copy still renders.

A picture is always a file from your media library: media:// followed by its id or its name. Anything the table does not list is refused, and so is anything over its limit, with a 400 schema_validation error that names the field.

Ask Reelwire for the whole JSON Schema, the document your content is checked against, without signing in:

curl "https://app.reelwire.io/v1/formats/template/tpl_b89f35e4a1f4?variant=Corporate%20glass&version=1.0.0"

Delivery JSON

Your own system sends this to one of your streams, POST /v1/stream, and every channel listening to that stream draws it with its template. data is the document described above; a stream with an empty field map passes it to the template unchanged. Try it first on POST /v1/stream/validate, which answers the same without publishing anything. Streams and feeds explains the rest, including how to map a document of your own shape instead.

{
  "streamId": "st_your_stream_id",
  "eventId": "01M2SQMKK3G1NVFXV31DCBVB95",
  "occurredAt": "2026-09-23T07:00:00Z",
  "locale": "en",
  "data": {
    "clipData": {
      "kicker": "Case study",
      "title": "How Harbour Logistics cut late deliveries by a third",
      "picture": {
        "alt": "A gradient of violet and blue standing in for the client's depot",
        "url": "media://example-image.jpg"
      },
      "pictureFit": "auto",
      "pictureFocus": "centre",
      "challengeLabel": "The challenge",
      "challenge": "Parcels ran late across three depots, and nobody could see where one was until it arrived.",
      "actionLabel": "What we did",
      "actions": [
        "Put every van and depot on one live map",
        "Moved routing to the morning's real orders",
        "Sent customers a two-hour delivery window"
      ],
      "resultLabel": "The result",
      "results": [
        {
          "unit": "%",
          "label": "fewer late deliveries",
          "value": 34
        },
        {
          "unit": "h",
          "label": "saved per driver each week",
          "value": 2.5
        },
        {
          "unit": "%",
          "label": "of parcels inside their window",
          "value": 96
        }
      ],
      "quote": {
        "text": "For the first time we know where every parcel is, and so do our customers.",
        "name": "Lena Marsh",
        "role": "Head of operations, Harbour Logistics"
      },
      "note": "Figures from Harbour Logistics, first quarter 2026",
      "styleWords": {
        "live": "LIVE",
        "byline": "By",
        "functionKeys": [
          "HELP",
          "DATA",
          "CHART",
          "NEWS"
        ],
        "commandKey": "GO",
        "realTime": "RT",
        "messageLabel": "MSG",
        "pictureLabel": "IMG"
      },
      "look": {
        "theme": "auto",
        "pace": "auto",
        "corners": "auto",
        "align": "auto",
        "logo": "auto",
        "logoSize": "auto",
        "hideHeader": false,
        "hideFooter": false,
        "pattern": "auto"
      }
    },
    "metaData": {
      "title": "How Harbour Logistics cut late deliveries by a third",
      "captionTiny": "Harbour Logistics cut late deliveries by 34%. One live map, routing on real orders and a two-hour window did it.",
      "captionShort": "How Harbour Logistics cut late deliveries by a third. Parcels ran late across three depots and nobody could see where one was. We put every van on one live map, moved routing to the morning's real orders and sent customers a two-hour window: 34% fewer late deliveries, 2.5 hours saved per driver a week.",
      "captionMedium": "How Harbour Logistics cut late deliveries by a third.\n\nThe challenge: parcels ran late across three depots, and nobody could see where one was until it arrived.\n\nWhat we did: every van and depot on one live map, routing moved to the morning's real orders, and a two-hour delivery window sent to every customer.\n\nThe result: 34% fewer late deliveries, 2.5 hours saved per driver each week, and 96% of parcels inside their window.\n\n\"For the first time we know where every parcel is, and so do our customers.\" Lena Marsh, Head of operations.",
      "captionLong": "How Harbour Logistics cut late deliveries by a third, in one quarter.\n\nThe challenge: parcels ran late across three depots, and nobody could see where one was until it arrived. Drivers planned their own routes the evening before, customers waited at home all day, and every complaint started with a phone call nobody could answer.\n\nWhat we did: we put every van and depot on one live map, so the team in the office sees what the drivers see. We moved routing to the morning's real orders instead of yesterday's plan. And every customer now gets a two-hour delivery window by text, updated as the van gets closer.\n\nThe result: 34% fewer late deliveries, 2.5 hours saved per driver each week, and 96% of parcels arriving inside their window.\n\n\"For the first time we know where every parcel is, and so do our customers,\" says Lena Marsh, Head of operations at Harbour Logistics.\n\nWant the same for your depots? Tell us where your parcels get stuck. Figures from Harbour Logistics, first quarter 2026.",
      "hashtags": [
        "casestudy",
        "logistics",
        "delivery",
        "results",
        "customerstory"
      ]
    }
  }
}

The delivery names no version: which build draws it is the channel's choice, the newest of its variant or the one it is pinned to. eventId is a ULID you make once per event: sending the same one again changes nothing. occurredAt is when the thing happened, not when you sent it. locale is the language of the text in data, and data.locales carries other languages beside it.