Changelog

What changed, in English, newest first.

An entry appears here when it changes something you can see or rely on: a new capability, a fixed defect, a different answer from an endpoint. Refactoring that nobody outside this page would notice does not get an entry, because a changelog nobody can act on is a list rather than a record.

**Breaking changes to /v1 are announced before they happen and get their own heading.** There have been none, and the moment there is one it will appear at the top of this page with a date it takes effect and what to change.

7 August 2026

The first public build

The API, the console and the command line are live at apublished.com. Everything below is available now.

What you can do today

• Schedule a post to one account or many, at a time you pick or at the next free slot in that account's own schedule.
• Repeat a post on a rule — daily, weekly, monthly — and get every occurrence as a real post on the calendar you can move, edit or cancel one at a time. Nothing is hidden behind a rule that evaluates later.
• Attach images and video, including files far too large for a browser form: uploads are resumable and resume from where they stopped.
• Import a folder of clips and a spreadsheet that names them, review every row, and commit the whole schedule in one step.
• Give an agent a key with only the permissions it needs, scoped to particular accounts if you want, and read the audit log of everything it did.
• Hold posts for a person to approve before they publish — automatic for any key that can write but not publish.

Platforms

The simulator is connectable now. It behaves like a real platform — the same delays, the same asynchronous publish, the same failures — so an integration can be written and exercised end to end before anything reaches an audience.

LinkedIn, Facebook, Instagram, TikTok and YouTube each have a complete adapter and are waiting on that platform's review of our application. They will appear as connectable options as approvals land, and each one gets an entry here on the day it does.

For agents

• GET /v1/capabilities — what each platform will and will not accept, as data, so a post is not composed by trial and error.
• POST /v1/posts:validate — check a post against every target without creating anything. Iterate until ok, then commit.
• [/llms.txt](/llms.txt), [/llms-full.txt](/llms-full.txt) and [/openapi.json](/openapi.json) — no auth, no JavaScript, stable URLs.
• An MCP server exposing the same operations as tools, and a TypeScript SDK and CLI.

Every error carries a machine-readable code and a remediation field. An agent that hits a limit is told which limit, what the current count is, and what would lift it, rather than being left to guess.

Punctuality

A post's dispatch is measured against the moment you asked for, and the number is on the status page rather than in a marketing claim. Media is uploaded and containers are created before the clock, so a large video does not push a post late.

Plans

Free, Creator, Studio and Agency. The free tier includes unlimited posting to the simulator on purpose — building the whole integration before paying is the point of it — and five real posts a month.

Earlier than this date, apublished was not publicly available and there is nothing here worth recording. The history exists in the repository; a changelog that begins before anybody could use the product would be a development diary wearing the wrong label.