Bump chart

How three to ten things change places over three to eight periods: the ranks stand down the start side and the periods across the top, every line draws period by period, crossing where one overtakes another, the one to follow in the brand colour, each name standing where it finishes, then a note: 10 to 15 seconds. In eleven styles, each wearing your brand's colours, fonts, logo, presenter and background.

Template id	`tpl_70698b5141c0`
Markets	Every market
Variants	Corporate glass, Bento grid, Broadcast news, Editorial, Swiss grid, Neo-brutalist, Soft friendly, Glitch cut, Hand marks, Outline, Infinite zoom
Ready-made feeds	None

Use cases

How rankings change: best sellers, most-used features, a league table.
Lines crossing as one overtakes another, the one to follow in your colour.
Three to eight periods, three to ten things.

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
Glitch cut	A dark page cut on the beat: heavy type sliced in, a split of your colours at every cut.	1	1.0.0
Hand marks	A clean page with a marker in your colours: loops, underlines and ticks drawn on over clean type.	1	1.0.0
Outline	Everything drawn as a line in your colours: outlined cards and bars that draw themselves on, only what matters filled solid.	1	1.0.0
Infinite zoom	Nested frames in your colours and one continuous push in: every part grows out of the middle, never a cut.	1	1.0.0

What it accepts

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

Bump chart: how three to ten things change places over three to eight periods, the ranks down the start side and the periods across the top, every line drawing period by period and crossing where one overtakes another, the one to follow in the brand colour and each name standing where it finishes. 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 title, the periods, the things and their ranks, the one to follow, the note, the source and the look.
`clipData.kicker`	text		up to 20 characters	Kicker: A word or two above the title, such as THE CHARTS.
`clipData.title`	text	yes	up to 80 characters	Title: What is ranked. Shown from the first frame.
`clipData.periods`	list	yes	at least 3, up to 8	Periods: Three to eight, oldest first: months, quarters, years, matchdays. Each adds a second.
`clipData.periods[]`	text		up to 10 characters	Period
`clipData.items`	list	yes	at least 3, up to 10	Things: Three to ten, each with its rank in every period, 1 the top. A rank left out leaves a gap in that thing's line.
`clipData.items[]`	group			Thing
`clipData.items[].name`	text	yes	up to 24 characters	Name
`clipData.items[].ranks`	list	yes	at least 3, up to 8	Ranks: One per period, in the same order as the periods: 1 for the top.
`clipData.items[].ranks[]`	integer		from 1, to 20	Rank
`clipData.items[].highlight`	boolean			Follow this one: Drawn in the brand colour and the others a step quieter, so it can be followed. Only the first one marked is.
`clipData.note`	text		up to 100 characters	Note: One line under the lines.
`clipData.source`	text		up to 70 characters	Source: Where the ranks come from, at the foot. Drawn exactly as written.
`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_70698b5141c0?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": "This year",
      "title": "Savings goals climbed to the most-used feature",
      "periods": [
        "Jan",
        "Feb",
        "Mar",
        "Apr",
        "May",
        "Jun"
      ],
      "items": [
        {
          "name": "Card payments",
          "ranks": [
            1,
            1,
            1,
            2,
            2,
            2
          ]
        },
        {
          "name": "Savings goals",
          "ranks": [
            5,
            4,
            3,
            3,
            1,
            1
          ],
          "highlight": true
        },
        {
          "name": "Budgets",
          "ranks": [
            2,
            3,
            2,
            1,
            3,
            3
          ]
        },
        {
          "name": "Transfers",
          "ranks": [
            3,
            2,
            4,
            4,
            4,
            4
          ]
        },
        {
          "name": "Investing",
          "ranks": [
            4,
            5,
            5,
            5,
            5,
            5
          ]
        }
      ],
      "note": "Ranked by how many customers used each feature in the month",
      "source": "Kite app figures",
      "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": "Savings goals climbed to the most-used feature",
      "captionTiny": "In January savings goals were our fifth most-used feature. By June they were the first.",
      "captionShort": "Savings goals were the fifth most-used feature in the app in January. Month by month they climbed, past investing, transfers and budgets, and in May they overtook card payments to become the feature you use most.",
      "captionMedium": "How the most-used features changed places this year:\n\nSavings goals: 5th in January, 1st since May.\nCard payments: 1st until March, now 2nd.\nBudgets: up to 1st in April, now 3rd.\nTransfers: 4th since March.\nInvesting: 5th since February.\n\nRanked by how many of you used each feature in the month.",
      "captionLong": "The feature you use most is no longer card payments.\n\nIn January savings goals were fifth. They climbed every month: past investing in February, past transfers in March, and in May past budgets and card payments to the top, where they stayed in June.\n\nCard payments are now second and budgets third, after a month at the top in April. Transfers have been fourth since March, and investing fifth since February.\n\nRanked by how many customers used each feature in the month. Thank you for saving with us.",
      "hashtags": [
        "saving",
        "features",
        "app",
        "fintech",
        "kite"
      ]
    }
  }
}

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.

Use cases​

Variants​

What it accepts​

Delivery JSON​

Use cases

Variants

What it accepts

Delivery JSON