Solid Growth will have one API for everything outside the app. It is not public yet. This page says what exists, what is coming and how it will behave.
One API
The app, the assistant and the MCP server already share one set of declarations, so a rule is written once. The public API follows the same idea: one API, with one resource per kind of record, instead of a separate API for each integration. The database views the app reads through are an internal detail and not a contract; do not build on them.
Authentication
Requests will act as a person and see only that person's workspaces, with the same roles as in the app. See Authentication.
What is live
| Endpoint | Purpose | Status |
|---|---|---|
/api/mcp | The MCP server, for a signed-in session. See MCP. | Live |
Resources per kind
| Resource | Status |
|---|---|
| Workspaces | Coming soon |
| Objectives | Coming soon |
| Key results | Coming soon |
| Initiatives | Coming soon |
| Deliverables | Coming soon |
| Tasks | Coming soon |
| Decisions | Coming soon |
| Requests | Coming soon |
| Cycles | Coming soon |
Each resource will be addressed by workspace and number, matching the addresses of the app. Paths, parameters and response shapes are published here when a resource ships; nothing is promised before that.