Industry events coming up (Pharmacies) (Countdown)

The pharmacy fairs and congresses coming up, with their dates and places: the next one with the two after it, every Monday. Dates are taken from each event's own site and the list is renewed every year.

Feed id	fd_fe68a5cf29bb
Type	Evergreen: Written once with AI, reviewed by a person, released on a schedule. Not news.
Plans	Every plan
Source	industry-events
Markets	Pharmacies
Schedule	Weekly, Mon 07:00
Template	Countdown, in whichever of its 10 visual variants a channel chooses when it adds the feed
Shapes	9x16, 4x5, 1x1, 16x9, 2x3
Languages	Any: translated by AI into the language each channel chooses
Freshness	An event older than 24 hours is kept but never published

Example video

The 1x1 cut of this feed's example, drawn in the Soft friendly 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

• 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.

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_fe68a5cf29bb"

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_fe68a5cf29bb",
  "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.