New: Steady API v2

A few weeks ago, we previewed Steady’s MCP server, the first major step in integrating Steady more tightly with your tools and workflows. Today we’re shipping the next step: a brand new, account-wide REST API.

Steady inherited its v1 API from Status Hero, along with the limitations: team-level instead of account-level, and mostly limited to check-ins. Customers have consistently asked for an API that can do more, so we started working on a clean-slate v2. It’s an account-wide, personally-scoped OpenAPI-compliant REST API that lets you work with all of Steady’s core data: your digest, check-ins, goals and goal updates, activity, Echoes, and more. You can read the API reference for the complete list of endpoints.

The v1 version isn’t going away any time soon — we’re not going to break anything for teams using it — but all of our efforts are going towards the v2 API moving forward.

Built around OpenAPI

We made a deliberate choice early on: the API would be OpenAPI-first, and the machine-readable spec would be the source of truth. If it’s in the spec, that’s how it works in production.

OpenAPI comes with some major benefits:

For people writing code. Point any tool that speaks OpenAPI 3 at our spec and you get something useful out the other side. Generate a typed client in your language of choice. Spin up a mock server to develop against. Import the spec into Postman, Bruno, or Insomnia and have a fully-loaded request collection in seconds.

For agents. A trustworthy spec is also a discoverability primitive. Hand the OpenAPI URL to an agent and it can introspect the surface at runtime — what endpoints exist, what parameters they take, what they return — and decide what to call without a hand-built integration for every workflow.

What you can do with it

• Custom dashboards. Pull recent check-ins, blockers, and goal updates into whatever internal reporting tool your team already uses.
• Export for ad-hoc analysis. Pull check-ins, activity, or goal updates out as JSON and load them into Excel, Google Sheets, or whatever your team uses to slice and dice data.
• Agents that handle your check-in. Point a script or agent at your recent commits, calendar, and tickets, and have it fill in your check-in for the day.
• Two-way sync with your system of record. Mirror Goal Story updates out to Notion, or pull Jira epics in as Goal Stories.

Because the API and our MCP server share the same underlying data and the same access model, the two are designed to feel like one platform with two front doors. Pick whichever fits the job.

Getting started

The API is available today for every Steady account. To get going:

1. Head to your personal connections page and generate a personal access token. Read-only tokens can live forever; tokens with write access expire within a year.
2. Point your tool of choice at https://service.steady.space/api/v2/ with an Authorization: Bearer <your-token> header.
3. Browse the API reference or import the OpenAPI spec into Postman, Bruno, Insomnia, or the OpenAPI client generator of your choice.

A note on security, same as with MCP: personal access tokens are personally scoped. Anything you can read or write through the API matches exactly what you can read or write in the Steady web app — nothing more, nothing less.

Bonus: a new webhook for collecting activity

Alongside the new API, we also launched a new webhook that makes it easy to collect activity for tools we don’t have first-party integrations for.

Turn it on in your account settings and you get a unique URL. POST a small JSON payload to it from anywhere — a Zapier zap, a cron job, another tool’s native webhook — to add your custom activity alongside other activity like GitHub PRs and Linear issues. See the webhook docs for the full payload format and setup details.