Skip to content

Content

Content is where your pages, components and their model live. From code you do three things: render published pages on your own site, author and publish from a script or an agent, and promote content between environments.

Ask Content which page is published at an address. The same call in the language you work in; your choice applies to every sample on this site.

Terminal window
curl "https://api.ebitex.io/content/delivery/v1/path/pricing?site=$SITE_ID" \
-H "Authorization: Bearer $EBITEX_DELIVERY_KEY"

You need a delivery key for your site. Set up your organization covers where each key is made.

Pick the track that matches what you are building.

Caching, Navigation, links and sitemaps, Streams, filters and search, Let editors preview drafts, Generate types from your content model, Keep your content model in git, Promote content from a pipeline, Replace a hand-written client.

The API reference covers the Delivery and Management APIs, for example resolve a path.

Package Registry Reference
@ebitex/content-sdk npm SDK reference
@ebitex/content-mcp npm SDK reference
@ebitex/starter-kit-react npm SDK reference
Ebitex.Content.Delivery NuGet .NET guide