Seven undocumented Forem API quirks that can break automated DEV publishing
A developer who published nine DEV.to articles entirely via the Forem API documented seven undocumented behaviours discovered through trial and error. Among the most significant: setting 'published: true' inside markdown front matter has no effect — the publish state must be passed as a separate JSON field on the article object. Similarly, attempting to update tags, title, or cover image via JSON fields is silently ignored on articles originally created with front matter; those fields can only be changed by rewriting the front matter within the full markdown body. The API also returns 'tag_list' inconsistently — as an array from one endpoint and a comma-separated string from another — and the listings and comments write endpoints either return empty responses or 404 errors without any useful feedback.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in