Build on ebitex
Render published content on your own site, author and publish content from a script or an agent, put forms in your own app, and know who your visitors are.
Start with what you are building
Section titled “Start with what you are building”A static siteVite and React, rendering published pages in the browser with @ebitex/content-sdk.
A server-rendered siteNext.js, with links and metadata in the HTML and your key kept on the server.
A .NET serverRender published content from ASP.NET Core with Ebitex.Content.Delivery.
Forms in your appEmbed a form with one script tag, or render it yourself with @ebitex/forms-sdk.
Already have your own client?What @ebitex/content-sdk handles that a hand-written Delivery client usually misses, and how to move over in steps.
Knowing your audienceIdentify a visitor from your server, resolve which audiences they are in, and read and write the people Audience holds.
Members-only pagesRestrict a page to an audience and serve it with a signed audience token.
Render an email from your siteServe the render protocol so Audience can turn one of your pages into an email.
Content as codeAuthor and publish from a script, a pipeline or an AI agent with a management key.
Reference
Section titled “Reference”API referenceEvery endpoint of the Content Delivery, Content Management, Audience and Forms SDK APIs.
SDK referenceThe exports of @ebitex/content-sdk, @ebitex/forms-sdk and @ebitex/content-mcp.
ErrorsEvery error code, what it means, and which operations return it.
OpenAPI documentThe machine-readable contract the API reference is built from, to generate a client or read an exact request shape.
SamplesComplete sites built on ebitex, to clone and run against your own organization.