Chirio
Get Started
Introduction
Quickstart
How Chirio works
Authentication
MCP server
Platforms
Overview
Instagram
Threads
X
LinkedIn
Supa Hub
Guides
Connect accounts
Publish a post
Media requirements
Carousels
First comments
Idempotency and retries
Account lifecycle
Revocation and deletion
The dashboard
Products
Screenshots
Feedback boards
What's new
Inbox
Messages
Site analytics
Page comments
Billing
Plans
Metering
Quotas
Api Reference
Overview
Accounts
Posts
Errors
Changelog
Roadmap
TrademarkTrademark
Ctrl k
Search…
Sign up
Chirio
Get Started
Introduction
Quickstart
How Chirio works
Authentication
MCP server
Platforms
Overview
Instagram
Threads
X
LinkedIn
Supa Hub
Guides
Connect accounts
Publish a post
Media requirements
Carousels
First comments
Idempotency and retries
Account lifecycle
Revocation and deletion
The dashboard
Products
Screenshots
Feedback boards
What's new
Inbox
Messages
Site analytics
Page comments
Billing
Plans
Metering
Quotas
Api Reference
Overview
Accounts
Posts
Errors
Changelog
Roadmap
TrademarkTrademark© Dopler. All rights reserved.
Built with Aveiro

What's new

A changelog on each board that your users read on the board and in the widget, written by your team or your agent.
Updated 4 days ago
Feedback boards
Inbox
Every board has a changelog. Your users read it at chirio.dev/b/your-board/changelog and in the widget's What's new panel, so they learn what shipped without visiting a blog. Your team writes entries in the dashboard; an agent writes them with an API key. It is included on every plan and costs no units.

Write an entry

curl https://chirio.dev/api/v1/changelog \
  -H "Authorization: Bearer chirio_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "board": "acme",
    "title": "Dark mode for the editor",
    "body": "The editor follows your system theme.\n\n- Toggle it in Settings\n- Exports keep their own colours",
    "tags": ["new"],
    "images": [{ "url": "https://cdn.example.com/dark-editor.png", "alt": "The editor in dark mode" }],
    "itemIds": ["8f2c..."]
  }'
An entry is a draft until you send publish: true. The body is plain text: a blank line between paragraphs, lines starting with - for a list, backticks for code. Tags are new, improved and fixed. An image is either { url }, an https image you already host (a screenshot result works), or , a PNG, JPEG or WebP data URL that Chirio stores. Keep the whole request under 4.5 MB.
{ data }

Close the loop

itemIds names the board posts the entry ships. Publishing moves the open ones to Done, with the resolution Shipped: and the entry's title unless one is set, and each post links to the entry. The people who voted see it shipped.

Edit, publish, take back

  • GET /api/v1/changelog?board=acme&status=published|draft lists entries.
  • GET|POST|DELETE /api/v1/changelog/:id reads, changes or deletes one. An update changes only the fields it names; images replaces the set, so send the current ones back by url.
  • publish: false takes an entry back to drafts. The first publish date stays.

Draw your own

The published feed is public, needs no key and allows any origin:
GET https://chirio.dev/api/boards/acme/changelog?limit=10 → { board, labels, latest, entries }

In the widget

The board widget adds a What's new button once an entry is published, with a dot until the visitor has seen the latest. data-changelog="false" turns it off, data-changelog-trigger="#selector" uses your own element (it gets data-chirio-unread="true" while there is news), and window.Chirio.openChangelog() opens it.

From an agent

The MCP server has list_changelog, create_changelog_entry and update_changelog_entry.