Now, next, later

A plan in three horizons without dates, what is done or under way now, what comes next and what follows later, up to four things each, each horizon lit in turn, side by side or one under the other, then a closing line: 16 seconds. In eight styles, each wearing your brand's colours, fonts, logo, presenter and background.

Template id	tpl_703b6a05d5bb
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 roadmap without promising dates: what is done, what comes next, what follows.
• A council's projects, a bank's coming changes or a shop's plans for the year.
• Your own words for now, next and later, and a closing line asking what should come next.

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.

Now, next, later: a plan in three horizons without dates, what is done or under way now, what comes next and what follows later, up to four things each, each horizon lit in turn, then a closing line. 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 words for the three horizons, what each holds, the closing line and the look.
clipData.kicker	text		up to 20 characters	Kicker: A word or two above the title, such as OUR ROADMAP.
clipData.title	text	yes	up to 80 characters	Title: What the plan is for. Shown from the first frame.
clipData.nowLabel	text		up to 16 characters	Word for now: Over the first horizon, in the language of the clip, such as Now or Jetzt. Left out, its number alone stands there.
clipData.nextLabel	text		up to 16 characters	Word for next: Over the second horizon, such as Next or Als Nächstes.
clipData.laterLabel	text		up to 16 characters	Word for later: Over the third horizon, such as Later or Später.
clipData.now	list	yes	at least 1, up to 4	Now: One to four things done or under way now.
clipData.now[]	group			Thing
clipData.now[].text	text	yes	up to 48 characters	What
clipData.now[].detail	text		up to 70 characters	Line under it: One line more about it.
clipData.next	list		at least 0, up to 4	Next: Up to four things that come next. Left out, the plan ends at now.
clipData.next[]	group			Thing
clipData.next[].text	text	yes	up to 48 characters	What
clipData.next[].detail	text		up to 70 characters	Line under it: One line more about it.
clipData.later	list		at least 0, up to 4	Later: Up to four things for later. Left out, the plan ends at next.
clipData.later[]	group			Thing
clipData.later[].text	text	yes	up to 48 characters	What
clipData.later[].detail	text		up to 70 characters	Line under it: One line more about it.
clipData.cta	text		up to 60 characters	Closing line: Shown once every horizon is in, such as where to say what should come next.
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_703b6a05d5bb?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": "Our roadmap",
      "title": "What is coming to the Kite app",
      "nowLabel": "Now",
      "nextLabel": "Next",
      "laterLabel": "Later",
      "now": [
        {
          "text": "Instant transfers to every bank",
          "detail": "Live for everyone since this week"
        },
        {
          "text": "Savings pots with goals"
        }
      ],
      "next": [
        {
          "text": "Shared accounts for couples",
          "detail": "Testing with a thousand customers"
        },
        {
          "text": "Round-ups into savings"
        }
      ],
      "later": [
        {
          "text": "Investing from the app"
        },
        {
          "text": "A card for your children"
        }
      ],
      "cta": "Tell us what you would like next in the comments",
      "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": "What is coming to the Kite app",
      "captionTiny": "Now: instant transfers and savings goals. Next: shared accounts. Later: investing. What would you like next?",
      "captionShort": "Here is what is coming to the Kite app. Now: instant transfers to every bank and savings pots with goals. Next: shared accounts for couples and round-ups into savings. Later: investing from the app and a card for your children. What would you like to see next?",
      "captionMedium": "Here is what we are building in the Kite app, and in which order.\n\nNow: instant transfers to every bank, live for everyone since this week, and savings pots with goals.\nNext: shared accounts for couples, which a thousand customers are testing, and round-ups into savings.\nLater: investing from the app and a card for your children.\n\nWhat would you like to see next? Tell us in the comments.",
      "captionLong": "Here is what we are building in the Kite app, and in which order, without promising dates we cannot keep.\n\nNow: instant transfers to every bank, live for everyone since this week, and savings pots with goals, so you can see how close you are to the holiday or the new bike.\n\nNext: shared accounts for couples, which a thousand customers are testing right now, and round-ups that put the change from every payment into savings.\n\nLater: investing from the app, and a card for your children with limits you set.\n\nWhat would you like to see next? Tell us in the comments: we read every one, and the plan changes because of them.",
      "hashtags": [
        "roadmap",
        "fintech",
        "comingsoon",
        "product",
        "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.