ZORALI logoLog in

Developers

The ZORALI API

Programmatic control over your sites: the API is organized around sites, pages, and elements, the same concepts you already know from the builder.

Start building freeBrowse templates

An API that mirrors the builder

The ZORALI API is designed around three core resources: sites, pages, and the elements on them. If you understand the builder's canvas, you already understand the API's mental model, a site contains pages, pages contain elements, and everything you can arrange visually is addressable programmatically. That symmetry keeps automation intuitive instead of arcane.

  • Sites, pages, and elements as the core resource model
  • The same concepts as the canvas, no second mental model to learn
  • Read and manage site structure programmatically
  • Built for automation, bulk operations, and integrations

What you can automate

The API targets the repetitive work that doesn't deserve clicking: spinning up pages from templates, syncing content from external systems, auditing site structure, and wiring ZORALI into deployment or content pipelines. Anything your team does the same way for the tenth time is a candidate for a script instead.

  • Generate pages and sections from templates at scale
  • Sync content from CMSs, databases, or internal tools
  • Audit and inventory sites, pages, and elements across projects
  • Wire publishing workflows into CI or content pipelines

Built for integrations

Because the API speaks the builder's language, integrations stay straightforward: your CRM, your content pipeline, or your client dashboard can manage ZORALI sites without screen-scraping or fragile workarounds. Agencies can build client-facing tooling on top of ZORALI; product teams can keep marketing pages in sync with the systems that own the data.

  • Connect ZORALI to CRMs, CMSs, and internal dashboards
  • Build client-facing tools on top of your ZORALI sites
  • Keep marketing content in sync with source-of-truth systems
  • Combine API automation with custom code embeds for full flexibility

Designed with developers in mind

The API follows resource-based conventions that feel familiar from day one: predictable resource shapes, standard authentication patterns, and errors that tell you what actually went wrong. It sits on the same Next.js + Supabase foundation as the rest of ZORALI, so behavior stays consistent between what you see in the builder and what you get from the API.

  • Resource-based design following familiar conventions
  • Consistent behavior between the builder UI and API responses
  • Same Next.js + Supabase foundation as the platform itself
  • Clear errors that point at the actual problem

Start with the builder, scale with the API

Most teams start visually, a template or an AI Studio draft, refined on the canvas, and reach for the API when a workflow repeats. That progression is intentional: the builder gets you shipping today, and the API keeps you fast as volume grows. Create, customize, save, and preview everything free on the Starter plan, and automate when you're ready.

  • Prototype visually first, automate the repeatable parts later
  • One mental model across canvas and code
  • Multi-site hosting included for everything you manage
  • Custom domains supported on Pro ($19/mo) and Business ($49/mo)
Start building free →

Frequently asked questions

→What is the ZORALI API?

It's ZORALI's programmatic interface, organized around the same concepts as the builder: sites, pages, and elements. It's designed for automation, bulk operations, internal tooling, and integrations with your existing stack.

→What can I build with it?

Page generation from templates at scale, content syncing from external systems, site audits and inventories, client-facing tooling for agencies, and publishing workflows wired into CI or content pipelines.

→Do I need the API to use custom code?

No, they're independent. Custom code blocks and embeds work entirely in the builder for adding your own HTML, CSS, and JavaScript to pages. The API is for programmatic management of sites and pages themselves.

→Is the API resource-based?

Yes. It's designed around familiar resource conventions, sites contain pages, pages contain elements, so it mirrors the builder's mental model and stays predictable to work with.

→Can agencies use the API for client work?

That's a core use case: agencies can build client dashboards and automated workflows on top of ZORALI, managing multiple hosted sites with custom domains from one account on Pro or Business plans.

→How much does API access cost?

Building in ZORALI starts free on the Starter plan. Paid plans are Pro at $19/mo and Business at $49/mo, which add publishing, hosting, and custom domains.

Ready to build with ZORALI?

Create, customize, and preview your site free. Take it live on a publishing plan when you're ready.

Get started freeExplore the marketplace