Skip to main content

Next public holiday in Peru (Countdown)

A countdown to the next public holiday in Peru, with the holidays after it, from the Nager.Date public holiday data.

Feed idfd_36cbecb6a0c6
TypeLive data: New data from public sources on every run. The wording may be polished and translated by AI.
PlansIndividual, Small business or Enterprise
Sourcepublic-holidays-and-seasonal-calendars
MarketsEvery market
ScheduleWeekly, Mon 06:00
TemplateCountdown, in whichever of its 10 visual variants a channel chooses when it adds the feed
Shapes9x16, 4x5, 1x1, 16x9, 2x3
LanguagesAny: translated by AI into the language each channel chooses
FreshnessAn event older than 24 hours is kept but never published

Example video​

The 1x1 cut of this feed's example, drawn in the Bento grid variant with an example brand. A channel draws it in the variant it chose and in its own brand. Open the video on its own.

Use cases​

  • A daily market wrap on the broker's own channels, out before the session opens.
  • Instrument moves and levels that introducing brokers and affiliates post under their own brand.
  • Economic calendar reminders: what is due today, and afterwards what it printed.
  • Release notes and product updates, published the day they ship.
  • Engineering or production figures as a weekly or monthly story with its numbers.
  • Trade fair and event countdowns for sales and partner channels.
  • Council and authority announcements, the moment they are published.
  • Dates people plan around: waste collection, opening hours, public events.
  • Open data made visible: air quality, water levels, traffic or budget figures.
  • New listings and price changes, posted the day they go live, with the property's key facts.
  • Mortgage rates and market figures for the area, as a weekly story agents post under their own brand.
  • Viewing days and open houses, counted down on every channel the agency runs.
  • Seasonal health reminders, such as pollen, UV and the flu season, posted when they matter.
  • Offers of the week and opening times, the on-call nights included.
  • Public holidays and changed hours, before customers have to ask.
  • This week's offers, per store, on every channel the shop runs.
  • Opening times and holiday changes, before customers have to ask.
  • Seasonal campaigns and price changes, drawn straight from the product data.

What it carries​

This feed carries what its template takes: the fields, what each may hold and a worked example are on the Countdown page, the same for every feed drawn with it. A picture is always a file from your media library: media:// followed by its id or its name. Anything the template 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 this feed is checked against, without signing in:

curl "https://app.reelwire.io/v1/formats/feed/fd_36cbecb6a0c6"

Which template draws a feed is Reelwire's decision and can change, so a producer asks by the feed, as above, rather than by its template.

Delivery JSON​

Every event of this feed is delivered to Reelwire in this envelope. You do not send it yourself: add the feed to a channel under Ready-made feeds, and each event becomes a post on that channel. data is the document described above, left empty here: the template's delivery JSON shows one filled in.

{
  "eventId": "01M2SQMKK3G1NVFXV31DCBVB95",
  "occurredAt": "2026-09-23T07:00:00Z",
  "feedId": "fd_36cbecb6a0c6",
  "locale": "en",
  "data": {}
}

feedId names this feed and never changes, even when the feed is renamed. eventId is set once per event, so an event delivered twice is published once. occurredAt is when it happened, which is what the freshness limit is measured from.