Caso de éxito

La historia de un cliente en tres pasos, una página cada uno: el reto, lo que se hizo en hasta tres pasos numerados y el resultado como hasta tres cifras que cuentan exactamente hasta el valor enviado, y después la cita del cliente; el título y una imagen en la portada: de 16 a 20 segundos. En ocho estilos, cada uno con los colores, fuentes, logo, presentador y fondo de su marca.

ID de la plantilla	tpl_b89f35e4a1f4
Sectores	Todos los sectores
Variantes	Corporate glass, Bento grid, Broadcast news, Editorial, Swiss grid, Neo-brutalist, Soft friendly, Keynote minimal
Feeds predefinidos	Ninguno

Casos de uso

• La historia de un cliente contada como prueba: qué iba mal, qué se hizo y las cifras que cambiaron.
• Un proyecto, un servicio o el despliegue de un producto, con hasta tres resultados que cuentan hasta exactamente lo que usted envía.
• Las propias palabras del cliente en una última página, con su nombre y cargo.

Variantes

Una variante es esta plantilla con otro diseño, y existe en versiones: compilaciones inmutables, la más reciente primero. Un canal sigue la versión más reciente de su variante, salvo que esté fijado a una.

Variante	Qué es	Versiones	Más reciente
Corporate glass	Tarjetas de cristal esmerilado sobre una aurora en los colores de su marca: tranquilo y premium.	1	1.0.0
Bento grid	Recuadros redondeados en los colores de su marca, cada uno con su propio movimiento: un aspecto moderno de producto.	1	1.0.0
Broadcast news	Un canal de noticias en sus colores: logotipo del canal en pantalla, rótulo inferior, teletipo y su presentador.	1	1.0.0
Editorial	Una página de revista con el tono de papel y la tipografía con serifa de su marca: cabecera, líneas finas y firma.	1	1.0.0
Swiss grid	Una cuadrícula estricta, tipografía grande y el color de su marca como único acento. Nada rebota.	1	1.0.0
Neo-brutalist	Bloques planos llamativos en sus colores con bordes gruesos y sombras duras.	1	1.0.0
Soft friendly	Formas suaves y tarjetas redondeadas en matices del color de su marca: cálido y cercano.	1	1.0.0
Keynote minimal	Un escenario de lanzamiento: una cosa cada vez, tipografía enorme y un barrido de luz en su color.	1	1.0.0

Qué acepta

Todas las variantes aceptan el mismo contenido, así que un documento se genera en cualquiera de ellas.

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.

Campo	Tipo	Obligatorio	Límite	Qué es
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	video		media:// picture or video from the media library, alt text up to 120 characters	Picture or video: The client, the place or the project, on the cover under the title. Left out, the title has the cover to itself. A video from the media library plays in its place, without its sound, and from its start again whenever it ends.
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 contiene otros idiomas: bajo cada código de idioma, las partes de clipData y metaData que cambian, superpuestas al contenido predeterminado, así que un idioma sin copia propia también se renderiza.

Una imagen es siempre un archivo de su biblioteca multimedia: media:// seguido de su ID o su nombre. Todo lo que la tabla no enumera se rechaza, y también todo lo que supera su límite, con un error 400 schema_validation que nombra el campo.

Pida a Reelwire, sin iniciar sesión, el JSON Schema completo, el documento con el que se valida su contenido:

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

JSON de entrega

Su propio sistema envía esto a uno de sus streams, POST /v1/stream, y cada canal que recibe ese stream lo genera con su plantilla. data es el documento descrito arriba; un stream con una asignación de campos vacía lo pasa a la plantilla sin cambios. Pruébelo primero con POST /v1/stream/validate, que responde igual sin publicar nada. Streams y feeds explica el resto, incluido cómo asignar en su lugar un documento con su propia forma.

{
  "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"
      ]
    }
  }
}

La entrega no nombra ninguna versión: qué compilación la genera lo elige el canal, la más reciente de su variante o la que tenga fijada. eventId es un ULID que usted crea una vez por evento: enviar el mismo otra vez no cambia nada. occurredAt es cuándo ocurrió el hecho, no cuándo lo envió. locale es el idioma del texto en data, y data.locales contiene otros idiomas junto a él.