Announcement Feed

The launcher shows a per-instance announcement banner. Dashboard instances manage it in the Announcements tab; self-hosted instances point metadata.announcementUrl at a JSON file. This page documents the feed format.

Where it comes from

metadata.announcementUrl (also mirrored as top-level announcementUrl) is fetched when the instance page opens, with the player's identity headers. The response is a bare JSON array; only entries with active: true are shown, newest first.

Loading diagram…

Dashboard instances use https://api.neko-launcher.com/api/v1/instances/<name>/announcements, which returns nothing for players who lack access to a locked instance.

Format

[
  {
    "title": "Scheduled maintenance",
    "category": "NOTICE",
    "link": "https://status.example.com",
    "active": true,
    "date": "2026-10-01T10:00:00.000Z",
    "metadata": {}
  },
  {
    "title": "Winter event is live",
    "category": "EVENT",
    "link": "https://example.com/events/winter",
    "active": true,
    "date": "2026-09-20T09:30:00.000Z",
    "metadata": {
      "th_title": "อีเวนต์ฤดูหนาวเริ่มแล้ว",
      "imageUrl": "https://cdn.example.com/winter-en.webp",
      "th_imageUrl": "https://cdn.example.com/winter-th.webp"
    }
  }
]
json

Localized keys follow the {lang}_{field} rule used everywhere in instance metadata: the launcher takes the player's language and falls back to the base field.

See also

• Announcements in the dashboard
• Instance configuration