Docs

https://feedfa.st/p/your-project

Changelog: the hub's default tab

https://feedfa.st/p/your-project/feedback

Feedback board

https://feedfa.st/p/your-project/status

Status page

https://feedfa.st/p/your-project/changelog/entry-slug

A single changelog entry

<script src="https://feedfa.st/embed.js" data-project="your-project" defer></script>

data-project

Required. Your project slug.

data-theme

auto (default) · light · dark

data-accent

Override the accent colour, e.g. #4F46E5

data-badge

false to turn the floating badge off

data-position

bottom-right (default) · bottom-left

data-user-id / -email / -name

Identify the signed-in user: see below

<button class="my-button" data-feedfast="feedback">
  Send feedback
</button>

The modal asks for a category, title, optional details and an optional email: the same fields as the public board, with the same rate limiting and spam trap. The submitted idea starts with the author's own upvote.

<button
  data-feedfast="feedback"
  data-user-id="${user.id}"
  data-user-email="${user.email}"
  data-user-name="${user.name}"
>Send feedback</button>

data-user-id

Your own user id. Opaque to us, never shown publicly.

data-user-email

Prefills the author, and makes their votes portable.

data-user-name

Shown as “Posting as …” in the modal.

data-user-hash

HMAC-SHA256 of the user id. Required once a secret is set.

Set the same attributes on the loader script to cover every trigger on the page, or call Feedfast.identify(...) once your SPA has the session. Identity on a trigger beats identity on the loader, so one page can have both an authenticated and an anonymous entry point.

Feedfast.identify({ id: user.id, email: user.email, name: user.name });
Feedfast.identify(null); // back to anonymous on sign-out

<div data-feedfast="uptime"></div>

data-monitor

Show a single monitor, by name

data-days

1–90. How much history to draw

data-compact

true | false: shorter bars

data-overall

true | false: the status line above the monitors

data-slim

true | false: drops the status line and the “View status page” link, and makes the whole badge the link instead. Implies data-compact unless you set it. Built for a site footer

<div data-feedfast="changelog" data-variant="card" data-limit="3"></div>

data-variant

card (default) | inline

data-limit

1–10. How many entries

data-excerpt

true | false: card variant only

data-tags

true | false: show tag pills

<!-- on by default -->
<script src="https://feedfa.st/embed.js" data-project="your-project" defer></script>

<!-- off, if you'd rather place widgets yourself -->
<script src="https://feedfa.st/embed.js" data-project="your-project" data-badge="false" defer></script>

The unread state lives in the visitor's own browser. If maintenance is scheduled, a notice appears above the entries.

data-badge is read once, when the script boots. In a single-page app that is the page the visitor first landed on, so a route change into a screen with no room for the badge: a dashboard, a checkout, anything with its own floating button in that corner: needs to say so:

Feedfast.setBadge(false);  // leaving a page that wants it
Feedfast.setBadge(true);   // and back

Safe to call before the script has finished loading only if you guard it, until then there is no window.Feedfast to call, and the attribute on the tag already describes the first page.

Feedfast.openFeedback(opts?)

Open the modal. { title, subtitle, user } frame it; { prefill } fills it in — see Feedback button → From code

Feedfast.openChangelog()

Open the “What's new” panel

Feedfast.setBadge(visible)

Show or hide the floating badge after load

Feedfast.identify(user)

Set the signed-in user; null clears it

Feedfast.close()

Close whatever is open

Feedfast.refresh()

Re-fetch and re-render every widget

Feedfast.mount(root?)

Scan for new widgets (usually automatic)

Feedfast.data()

The current payload, or null before first load

Set it on the monitor, under Uptime → the monitor → Authentication. Three methods, which between them cover most APIs:

Bearer token

Sent as Authorization: Bearer <token>.

Custom header

Any header name you like, e.g. X-API-Key.

Query parameter

Appended to the URL, e.g. ?token=…

What your endpoint receives, so you know what to compare against. Prefer the bearer form: a token in a URL ends up in your own access logs, and in any proxy in front of them.

GET /api/health HTTP/1.1
Host: your-app.com
Authorization: Bearer <your token>
User-Agent: FeedFast-Monitor/1.0 (+https://feedfa.st)

Your token is encrypted before it is stored and is never shown again — the form only knows whether one is saved. Leave the field blank when editing a monitor to keep the existing token, or type a new one to replace it. If a check ever reports that the credential cannot be read, re-enter it: that means the deployment's signing secret changed.

https://feedfa.st/p/your-project/rss.xml

Published changelog entries

https://feedfa.st/p/your-project/status.rss

Incidents and maintenance windows

GET https://feedfa.st/api/widget/your-project

No auth required

{
  "project":  { "name": "Acme Analytics", "slug": "acme", "accentColor": "#4F46E5" },
  "hubUrl":   "https://feedfa.st/p/acme",
  "modules":  { "changelog": true, "feedback": true, "status": true },
  "entries":  [{ "id": "…", "title": "…", "url": "…", "excerpt": "…",
                 "tags": ["New"], "publishedAt": "2026-08-14T05:12:59.305Z" }],
  "categories": [{ "id": "…", "slug": "bug", "name": "Bug",
                  "color": "#EF4444", "isDefault": false }],
  "uptime": {
    "overall":  { "state": "operational", "label": "All systems operational" },
    "monitors": [{ "name": "API", "state": "up", "uptimePct": 99.82,
                   "bars": "uuuuuuuuduuu…" }],
    "days": 90, "startDay": "2026-05-19", "timezone": "Europe/Bucharest"
  },
  "maintenance": { "title": "Database upgrade", "status": "SCHEDULED",
                   "startsAt": "2026-08-19T08:41:12.638Z",
                   "endsAt":   "2026-08-19T09:41:12.638Z" }
}

Each character in bars is one day, oldest first: u up, d down, g degraded, m maintenance, n no data. Every timestamp is ISO 8601 in UTC.

?category=bug

One category, by slug

?category=bug,feature-request

Several categories

?status=open,planned

Filter by status

?sort=top | new | trending

Top votes (default), newest, or votes in the last 7 days

?q=slack

Free-text search across title and body

Subscriptions are double opt-in (the address only receives mail after the confirmation link is clicked) and every email carries a one-click unsubscribe link.

Subscribers are emailed when an incident opens or resolves, and at whichever maintenance milestones you enabled (scheduled, started, completed).

Keys look like ff_…. Only a SHA-256 hash is stored, so the plaintext is shown exactly once, at creation.

curl https://feedfa.st/api/v1/projects \
  -H "Authorization: Bearer ff_your_key_here"

Scope

READ_ONLY or READ_WRITE, writes 403 on a read-only key

Rate limit

120 requests per minute per key

Reach

Every project on the account that owns the key

GET /api/v1/projects

Every project this key can reach

GET /api/v1/projects/:slug/changelog

?status=&limit=

POST /api/v1/projects/:slug/changelog

Create, and publish by default

PATCH /api/v1/projects/:slug/changelog

Edit, publish or unpublish

GET /api/v1/projects/:slug/feedback

?category=&status=&sort=&q=&limit=

GET /api/v1/projects/:slug/feedback/:postId

One post with its comment thread

PATCH /api/v1/projects/:slug/feedback

Status, category, pin, owner reply

POST /api/v1/projects/:slug/feedback/:postId/resolve

Close it, reply, and publish the changelog entry in one transaction

GET /api/v1/projects/:slug/uptime

?days=, state, uptime windows, incidents

GET /api/v1/projects/:slug/maintenance

?upcoming=true

POST /api/v1/projects/:slug/maintenance

Schedule a window

PATCH /api/v1/projects/:slug/maintenance

start | complete | cancel

curl -X POST https://feedfa.st/api/v1/projects/acme/maintenance \
  -H "Authorization: Bearer ff_…" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Database upgrade",
    "startsAt": "2026-09-01T02:00",
    "endsAt":   "2026-09-01T03:30",
    "timezone": "Europe/Bucharest",
    "monitors": ["API"]
  }'

claude mcp add --transport http feedfast https://feedfa.st/api/mcp --header "Authorization: Bearer ff_your_key_here"

{
  "mcpServers": {
    "feedfast": {
      "type": "http",
      "url": "https://feedfa.st/api/mcp",
      "headers": {
        "Authorization": "Bearer ff_your_key_here"
      }
    }
  }
}

claude mcp add feedfast --env FEEDFAST_API_KEY=ff_your_key_here -- npx -y feedfast-mcp

{
  "mcpServers": {
    "feedfast": {
      "command": "npx",
      "args": [
        "-y",
        "feedfast-mcp"
      ],
      "env": {
        "FEEDFAST_API_KEY": "ff_your_key_here"
      }
    }
  }
}

[mcp_servers.feedfast]
command = "npx"
args = ["-y", "feedfast-mcp"]
env = { FEEDFAST_API_KEY = "ff_your_key_here" }

list_projects

Slugs, enabled modules and content counts

get_uptime

Monitor state, uptime windows, open and recent incidents

list_feedback

Filter by status, category, search; sort by top/new/trending

get_feedback

One post with its full comment thread

update_feedback

Status, category, pin, and public owner replies

resolve_feedback

Close the loop: mark it done, reply publicly, publish the changelog entry, link them

list_changelog

Published and draft entries

publish_changelog

Write a release note, public immediately

update_changelog

Edit, publish a draft, or unpublish

list_maintenance

Scheduled, in progress and completed windows

schedule_maintenance

Announce planned downtime

transition_maintenance

Start now, complete early, or cancel