Using Zendesk Article API, how do I get the latest article draft, and not the published body? | Community
Skip to main content

Using Zendesk Article API, how do I get the latest article draft, and not the published body?

  • September 6, 2024
  • 5 replies
  • 0 views

Bienvenido

I have a published article with a more recent edited, unpublished draft. Using the Articles API, I can't seem to get the most recent draft body. I always get the older published body when using the API.

 

https://developer.zendesk.com/api-reference/help_center/help-center-api/articles/

 

How do I use the Articles API so I can get the most recent unpublished draft?
 

5 replies

  • September 9, 2024

Hi David!

 

Currently, the Articles API only accesses published articles. Zendesk doesn't have an API for article management states such as a draft. 


Bienvenido
  • Author
  • September 10, 2024

Thanks Erica.


  • February 18, 2025

@erica26 Are there any plans to add any level of support for the article management and review workflow? 

It's a very painful limitation for the API to ignore published articles with edits in progress (in progress, awaiting review, ready to publish). We use that workflow pretty heavily and it makes the API unreliable for us to manage our content holistically.

 


  • February 24, 2025
Hi Ben, 
 
I recognize that this is an important feature request for you. Unfortunately, I don't have a definitive answer as to if this will be implemented. However, I do recognize the importance ion having such collaboration tools. I recommend sharing this as a post in our Product Feedback for our Developer Platform. Our product teams use these posts as a resource for product and feature planning. 
 
Thoughtfully shared use cases and business needs are always appreciated. 

  • April 22, 2025

Hey @ben32 @bienvenido — curious to hear if you’ve come up with any clever workarounds or hacks for the lack of access to “in progress,” “awaiting review,” or “ready to publish” statuses.

We’ve got a few LaunchBrightly clients syncing updated screenshots, but without visibility into in-progress content, it's tricky. We’ve landed on a tagging-based approach—it adds a bit of manual overhead, but gives us the flexibility we need.

Anywho, eager to hear how you might be navigating this constraint! 🙂