Block-type Dynamic Content is currently invisible to the Articles API; inline is partially visible
We use the Articles API (get_article/update_article) to manage bulk content updates across our Help Center, and we ran a few tests to understand how Dynamic Content interacts with it.
Inline Dynamic Content is represented in the body field returned by get_article as a placeholder token:
#{{dynamic_content:content-name}}
This at least tells us a reference exists and its name, even though the resolved value stays UI-only.
Block-type Dynamic Content is completely absent from the API response regardless of whether the block holds text or an image. We confirmed this with three separate tests in the same article: a block-type text entry, an inline-type text entry, and an image inserted as a block. Only the inline entry appeared in the API body; the block-type text and the image were both invisible, even though all three render correctly in the editor and on the live page.
This inconsistency matters for any team managing a Help Center via API-driven workflows: block-type usage is completely undetectable programmatically. A script auditing or updating article content has no way to know an article contains a block-type Dynamic Content reference.
Requests, in order of usefulness to us:
Represent block-type Dynamic Content in the API body the same way inline is handled with a placeholder token.
Longer-term: expose a Dynamic Content read API so external tools can detect and enumerate usage across both types.