Developers

Who this page is for

Almost nobody using Siteleon needs it. It exists for agencies running many client workspaces, for in-house developers connecting a system that has no ready integration, and for anyone who wants to know what is programmable before they commit.

The API

A REST API over the same objects the product uses: sites, pages, forms, business knowledge, leads, insights and releases. It is scoped per workspace and per token, and a token can never exceed the permissions of the person who created it.

• Read and write business knowledge
• Create and update pages and their sections
• Read form submissions and leads
• Read insights and analytics
• Trigger and read releases

The site connector

A first-party script for a site Siteleon did not build, plus a WordPress plugin, a Shopify app and a Webflow embed that wrap it. It serves from your own domain, which is why the measurement survives the browser restrictions that break third-party tags.

Webhooks

Subscribe to the events that matter operationally: a new enquiry, a form that stopped delivering, a release published, a business fact changed, an insight raised. Delivery is retried, and every delivery is recorded so you can tell a missed webhook from one that never fired.

Rate limits and quotas

Limits are per workspace and per token, and are a plan property rather than a surprise. Where a limit is hit, the response says which one and when it resets rather than failing opaquely.

What is deliberately not exposed

There is no endpoint that bypasses approval policy, and none that lets a token act outside its own permission scope. An automated integration that could publish a price change without review would make the approval model decorative.