Delivery API

The HTTP surface behind the SDK.

The SDK is a thin wrapper. Anything it does can be done with fetch, which is what non-JavaScript stacks do.

Fetch one entry

http

GET /api/delivery/:publicKey/entry?model=page&url=/pricing

Query parameters:

Name	Meaning
`model`	content model, usually `page`
`url`	the page's URL path
`variants`	JSON object of flag key to variant
`attributes`	JSON object of personalization attributes
`preview`	`1` to read the draft; requires a preview token

Returns the resolved entry: variant content merged, personalization applied, hidden blocks removed.

List entries

http

GET /api/delivery/:publicKey/entries?model=page&limit=50

For sitemaps and index pages. Returns metadata, not full content.

Redirects

http

GET /api/delivery/:publicKey/redirect?url=/old-path

Returns the target and status code, or 404. Authors manage redirects alongside pages so a URL change does not need a deploy.

Errors

Errors come back as { error: { code, message } } with a real status code. The SDK's fetch helpers return the error object rather than throwing, so a delivery hiccup renders your fallback instead of a 500.

All documentation · llms.txt · llms-full.txt · contentbind.com