Format
Focused questions and practical troubleshooting
Learn the difference between draft preview and published delivery and how to debug mismatches.
AI Summary
Learn the difference between draft preview and published delivery and how to debug mismatches.
Quick Facts
This snapshot gives the page context in a fast, scannable format.
Format
Focused questions and practical troubleshooting
Interview practice
Use these explanations to practice the mechanism and a safe diagnostic sequence.
The Content Delivery API serves published content. The Preview API provides the latest drafts as well as published content for preview, and uses a separate preview access token. Preview is intended for authorized editorial workflows.
Compare the entry ID, space, environment and locale in both requests. Check whether the changed entry and necessary references are published. If the Delivery API response is current but the rendered page is stale, investigate the application cache and revalidation.
Keep preview access limited to authorized users and avoid exposing preview tokens in public client bundles, logs or public responses. Store credentials in an appropriate server-side secret store and rotate a token if it is exposed.
A requested locale can use a configured fallback when a field has no value. Inspect the requested locale, the fallback chain and the API response. Locale publishing status is a separate concern, particularly when locale-based publishing is enabled.
Continue learning
Connect the focused answers with the broader practice track.
Sources
Use these references to keep the guide grounded in official product documentation and the most relevant SplashRide pages.