Skip to content
Rapcord
← All docs

Developer API and self-hosting

Last reviewed 2026-10-23

Rapcord's official API and updater are operated by this website's Lovable Cloud project. All endpoints live under https://updater.rapcord.dev/api/public/v1.

Public endpoints

  • GET /api/public/v1/health — service status.
  • GET /api/public/v1/config — API base URL, supported platforms, minimum client version, feature flags.
  • GET /api/public/v1/updates/latest?platform=win32&arch=x64 — latest published release manifest.
  • GET /api/public/v1/releases — all published releases.
  • GET /api/public/v1/download/win32/x64/Rapcord-<version>-Setup.exe — redirects to the installer file.
  • GET /api/public/v1/badges — enabled badge definitions.
  • GET /api/public/v1/badges/<discordId> — badges for one Discord ID.

Manifest fields

{
  "schema": 1,
  "version": "1.2.3",
  "platform": "win32",
  "arch": "x64",
  "notes": "What's new",
  "size": 84213760,
  "sha256": "64 lowercase hex characters",
  "url": "https://updater.rapcord.dev/api/public/v1/download/win32/x64/Rapcord-1.2.3-Setup.exe",
  "publishedAt": "2026-10-23T12:00:00Z"
}

The download link redirects once to a short-lived storage link. Clients must follow at most a few HTTPS redirects, enforce the size limit and verify sha256 before opening the file.

Publishing

Admins create a draft, upload the .exe, review its size and SHA-256 and then publish explicitly. Older releases stay available for rollback.

Forks

A fork owner needs their own Lovable Cloud project: auth and owner bootstrap, a private storage bucket with admin-only upload rules, the database tables and policies, allowed origins, and their own API URL configured in the Rapcord client. Never publish service keys.

Related