Delivery

Choose which channels see an entry, let applications read a content space, check what they receive, call the delivery API, and fix content that doesn't arrive.

Showing 5 articles for everyone.

Set up delivery

2 articles
Guide Give an application access to a content space Register the website or app in API Consumers and issue its key, grant it one or more content spaces with a default channel, then turn its access off, remove it, or move it to a newer schema version. For Administrator, Developer Guide Show content on chosen channels only Add delivery channels such as Web, Android, iOS and Kiosk, show an entry on some of them only, and understand what an application that names no channel receives. For Administrator, Team member

For developers

2 articles
Reference Delivery API: addresses, parameters and responses The public delivery API's two addresses, how to send a key, every query parameter, the JSON a Single, a Collection and one item return, status codes, caching, CORS and rate limits. For Developer Guide See what an application receives in the API explorer Run any delivery request as an anonymous visitor or as a granted application, see which of the eight checks pass, copy the request as curl or fetch, and preview drafts before anyone receives them. For Administrator, Team member, Developer

Fixes

1 article
Troubleshoot An application doesn't receive your content A website or app gets "not found", 401 or 422, still shows the old version, or misses a field or a translation. Find which check fails and fix it. For Administrator, Team member, Developer