Status Badges
Embeddable SVG badges for your tasks, monitors, and endpoints. Show live status in READMEs, dashboards, or status pages.
Overview
Every recurring task (cron), monitor, and endpoint can have a public badge enabled from its detail page. When enabled, a unique token is generated and two SVG badge URLs become available:
- Status badge — a shields.io-style flat badge showing the current state
- Uptime bars — a bar chart of recent executions or daily status
Badges are publicly accessible via their token URL — no API key or login required. Disable the badge at any time to revoke access.
Enabling a Badge
- Open the detail page of a recurring task, monitor, or endpoint
- Scroll to the Public Badge section
- Click Enable Badge
- Copy the markdown or URL from the embed snippets
Badge URLs
Once enabled, your badges are available at these URLs (replace TOKEN
with the generated token):
Task badges (cron only)
https://runlater.eu/badge/task/TOKEN/status.svg https://runlater.eu/badge/task/TOKEN/uptime.svg
Monitor badges
https://runlater.eu/badge/monitor/TOKEN/status.svg https://runlater.eu/badge/monitor/TOKEN/uptime.svg
Endpoint badges
https://runlater.eu/badge/endpoint/TOKEN/status.svg https://runlater.eu/badge/endpoint/TOKEN/uptime.svg
Embedding
Markdown (GitHub, GitLab, etc.)
 
HTML
<img src="https://runlater.eu/badge/task/TOKEN/status.svg" alt="Status" /> <img src="https://runlater.eu/badge/task/TOKEN/uptime.svg" alt="Uptime" />
Badge Types
Status badge
A flat, shields.io-style badge with two sections: the resource name on the left and its current status on the right.
| Resource | Possible values |
|---|---|
| Task (cron) | passing, failing, timeout, running, paused, unknown |
| Monitor | up, down, degraded, paused, new |
| Endpoint | passing, failing, timeout, running, disabled, no data |
Uptime bars
A horizontal bar chart showing recent history. Each bar represents:
- Tasks (cron) — one bar per execution (last 50). Green = success, red = failed, orange = timeout.
- Monitors — one bar per day (last 30 days). Green = up, orange = degraded, red = down.
- Endpoints — one bar per inbound event (last 50). Color reflects forwarding execution status.
Caching
Badge responses include a Cache-Control: public, max-age=60 header.
This means CDNs, browsers, and proxies will cache the badge for up to 60 seconds.
Status updates will appear within a minute.
Security
- Badges are opt-in — disabled by default, must be explicitly enabled per resource
- Each badge uses a unique, unguessable token (24 hex characters)
- Disabling a badge clears the token — the old URL immediately returns a 404
- Badges only expose the resource name and status — no URLs, headers, response bodies, or other sensitive data