July 2026 Update

Contentful Preview and Delivery API Interview Questions

Learn the difference between draft preview and published delivery and how to debug mismatches.

AI Summary

AI Summary / TLDR

Learn the difference between draft preview and published delivery and how to debug mismatches.

Quick Facts

What to Know Before You Go Deeper

This snapshot gives the page context in a fast, scannable format.

Format

Focused questions and practical troubleshooting

Interview practice

Questions and answers

Use these explanations to practice the mechanism and a safe diagnostic sequence.

What is the difference between the Delivery and Preview APIs?

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.

Preview shows a change but the live page does not. What next?

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.

How should preview credentials be handled?

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.

How can locale fallback affect debugging?

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.

Sources

Sources / References

Use these references to keep the guide grounded in official product documentation and the most relevant SplashRide pages.