Skip to main content

Intro, Index tabs

In the Index tabs style: filed cards with coloured tabs, one rising from the stack.

TemplateIntro, tpl_efa56706d52d
VariantIndex tabs
Version1.0.0, the newest: what a channel following this variant draws
Shapes9x16, 4x5, 1x1, 16x9, 2x3
Length4 seconds

Example video​

The 1x1 cut of this variant, drawn from its own worked example. Open the video on its own.

What it accepts​

A four-second logo reveal: the brand's logo, its name where asked, and a slogan. metaData is the post's title, descriptions and hashtags and is never drawn.

FieldTypeRequiredLimitWhat it is
clipDatagroupyesClip data: Everything drawn besides the brand's logo: the slogan, whether the brand's name stands beside the logo, how the logo is revealed, how the intro ends, and the look.
clipData.slogantextup to 60 charactersSlogan: A line under the logo, such as what the brand promises. Left out, the intro is the logo alone.
clipData.showNamebooleanBrand name beside the logo: Writes the brand's name beside or under the logo in its headline face. A brand with no logo always shows its name.
clipData.revealenumauto, assemble, unveil, impactReveal: How the logo appears. Every style does all three in its own way: assembled from its pieces, uncovered by a wipe, a mask or light, or landing with an impact.
clipData.endingenumhold, clearEnding: Hold keeps the logo to the last frame, for a straight cut into the video. Clear lets everything leave over the last half second, so the video starts from the style's own background.
clipData.styleWordsgroupStyle 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. Each style draws only its own.
clipData.styleWords.realTimetextup to 12 charactersReal-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.titleBlocktextup to 16 charactersTitle block label (Blueprint): Written above the label in Blueprint's title block, such as TITLE. Left out, the block holds the label alone.
clipData.lookgroupLook: How the intro looks and moves within its style. Leave a switch out, or set it to the style's own, and the style decides.
clipData.look.themeenumauto, brand, light, dark, boldTheme: The style's own choice; your brand's own colours; a light or dark page tinted with your brand colour; or your brand colour as the page.
clipData.look.paceenumauto, calm, standard, punchyPace: How things arrive: the style's own rhythm, calm fades, a standard rhythm, or punchy slams and cuts.
clipData.look.cornersenumauto, square, soft, roundCorners: The shape of cards, panels and marks.
clipData.look.alignenumauto, start, centreText alignment: Where the text lines up.
clipData.look.logoenumauto, freeLogo: 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.logoSizeenumauto, small, largeLogo 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.backgroundbooleanBrand background: Draws your brand's background picture or film in place of the style's own moving background, under a veil of the theme's page so the words stay readable. It needs a background switched on in your brand's settings; without one, the style's own background is drawn.
metaDatagroupMeta 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.titletextup to 100 charactersTitle: 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.captionTinytextup to 200 charactersTiny description (Pinterest, Threads, X): Up to 200 characters. The brand's description, link and hashtags follow it within the platform's limit.
metaData.captionShorttextup to 500 charactersShort description (Telegram, Threema, WeChat, WhatsApp): Up to 500 characters. The brand's description, link and hashtags follow it within the platform's limit.
metaData.captionMediumtextup to 1500 charactersMedium 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.captionLongtextup to 4000 charactersLong description (Facebook Feed, YouTube): Up to 4000 characters. The brand's description, link and hashtags follow it within the platform's limit.
metaData.hashtagslistup to 15Hashtags: Written without the #. Up to 15, which every platform takes.
metaData.hashtags[]textup to 60 charactersHashtag

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_efa56706d52d?variant=Index%20tabs&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": {
"slogan": "Clear numbers, every day",
"showName": true,
"reveal": "auto",
"ending": "hold",
"styleWords": {
"realTime": "RT",
"titleBlock": "TITLE"
},
"look": {
"theme": "auto",
"pace": "auto",
"corners": "auto",
"align": "auto",
"logo": "auto",
"logoSize": "auto",
"background": false
}
},
"metaData": {
"title": "Welcome",
"captionTiny": "Welcome.",
"captionShort": "Welcome to our channel.",
"captionMedium": "Welcome to our channel. Follow for more.",
"captionLong": "Welcome to our channel. Follow for more, every week.",
"hashtags": [
"welcome"
]
}
}
}

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.