Platform Integrations

Folder structure

Both platforms use the same convention. Clips are filed by competition, then by event, inside the folder you choose.

Layout

<your chosen folder>/
│
├── Premier League 2026-27/                 ← tournamentName
│   ├── Manchester City vs Arsenal/         ← streamName
│   │   ├── Penalty save 68'_16x9_en.mp4
│   │   ├── Penalty save 68'_9x16_en.mp4
│   │   ├── Opening goal 12'_16x9_en.mp4
│   │   └── Opening goal 12'_16x9_ar.mp4
│   │
│   └── Liverpool vs Chelsea/
│       └── …
│
└── Opening Ceremony, Main Stage/           ← no tournament, so one level up
    └── …

text

# path      {tournamentName}/{streamName}/
# filename  {name}_{aspectRatio}_{language}.mp4

The aspect-ratio and language suffixes keep renditions of one clip distinct within a flat folder.

Streams with no tournament are filed directly under your chosen folder, so expect both depths in the same tree. Tell us if you would rather split by aspect ratio, by language, or drop the tournament level entirely.

Naming rules

Names are sanitized: Titles are typed by operators, so characters illegal in a path become hyphens and each component is capped at 120 characters. A competition sent as Premier League 2026/27 therefore becomes the folder Premier League 2026-27.
Nothing is overwritten: A name collision is delivered with a numeric suffix rather than replacing the existing file.
Names are not identifiers: An operator may rename a clip after delivery, and two clips in one event can share a name. Use the webhook if you need a stable key.