Description:
We publish Zendesk Guide articles, then prepare draft updates ahead of coordinated product launches. Our product has in-app localized links, and we release all languages simultaneously, so we must localize these draft updates before launch.
Currently, once an article is published, the API does not allow us to:
- Detect that unpublished changes exist
- Retrieve the draft body for localization/QA
We’re forced to duplicate articles as a workaround, which risks broken links, wrong IDs, and launch errors.
Expected:
- An API flag to indicate a draft exists (has_draft: true)
- Ability to retrieve draft content (title, body, metadata) via parameter or version selector (e.g., ?version=draft)
- No ID/URL change upon publish
Impact:
- Delays localization, forcing English-only launches or post-launch fixes
- High risk of mismatched locales and broken in-product links
- Prevents synchronized multilingual releases
This is critical for maintaining accuracy, consistency, and launch readiness across all locales.