API-First, and the Docs Are Public

MooverApp has no private API. The panel our customers work in is a client of the same public interface your own code can call — accounts, websites, pages, blocks, menus, blog posts, media, themes, languages and settings are all resources, and there is nothing the panel can do that a request cannot.

That interface is now documented in the open at dev.moover.app: the whole reference, a playground that makes real calls, and OpenAPI files to point your own tools at. Reading it needs no account.

Learn one resource, predict the rest

Everything on the platform follows one set of rules: five standard methods on every resource, the same field naming, the same paging, filtering and ordering parameters on every list, one error format, and one way to keep two editors from overwriting each other. When the work outlives the call — provisioning a new site, for instance — you get an operation to poll instead of a connection held open.

The documentation cannot drift

The reference is generated from the declarations the service itself is built from, in the same build, and shipped by the same release. The description of an endpoint and the code that answers it are one commit: rename a field and the page describing it changes with it, or the build fails. There is no second document to keep in step, and nothing to forget.

The examples work the same way. The requests in the quickstart are regions of one script we actually run — ten steps from an empty account to a page on a live domain — so a broken example is a broken build rather than a support ticket.

Your sites are readable by machines too

Being API-first does not stop at the editor. Every site the platform renders can also serve a read API, a Markdown twin of each page, an MCP endpoint and a discovery catalog — so an assistant asked about your content gets the content instead of scraping your layout. Each of those is a switch in your settings, next to the one that says what AI systems may do with what they read.

Where to start

Open the developer portal, run the quickstart, and sign the playground in with the same credentials you use for the panel. Built something on it? Tell us — we read what gets built on the platform.