Built and Published No-Code Sites via Builder API

Standing up a no-code site has meant working record by record in the admin, with no safe way for an agent or script to assemble a whole site and hand it back for review. A new Builder API now lets agents and scripts create records, lay out pages, set navigation and redirects, tune the design, and publish a complete website-builder site through a single REST surface, so an entire draft site can be assembled programmatically and checked before anything goes live. Every change is draft-first, so generation never publishes on its own.

A predictable way to assemble a site

Work is grouped into changesets, and each changeset applies its operations in all-or-nothing batches: if any operation in a batch fails, Basker rolls the whole batch back, including any records it had already created, so a half-built site can never be left behind. You can create, update, upsert, and archive records, add and arrange page blocks, import media, and set navigation, redirects, and SEO, all referenced by stable aliases and handles so later steps can point at records the same request just created. The API is deterministic and idempotent, so re-running the same work does not duplicate content.

Safety before anything changes

Every operation can run as a dry run first, returning a result that detects drift, so a script can confirm the site is still in the state it expected before it commits a single write. Discovery endpoints let an agent read a site's current structure, schemas, required fields, and existing records up front, which keeps generated content grounded in what the collection actually accepts rather than guesswork. Together these mean a run either lands cleanly or stops with a clear diagnostic instead of writing partial content.

Review, publish, and roll back

Before publishing, a review package gathers everything the changeset will change into a single stable summary so you can see the full scope of a release in one place. Publishing runs in two steps, a plan and then the publish itself, and the same applies to rollback, so a release can be reversed cleanly if you need to step back. Access is gated by API key scopes and is limited to sites running in no-code mode, so the Builder API only ever touches the sites it is meant to.