CMS Write API
Map a reviewed editorial record into a destination-specific publishing system.
A CMS adapter should translate content, not decide what the article is allowed to say. Keep generation, approval, and destination writes separate. Different content systems have different fields and editorial behavior, so define the mapping for the installation you actually control instead of assuming one universal payload.
Document the field mapping
Map title, body format, excerpt, authorship, taxonomy, media, and status. Keep internal review notes out of public fields. Store the destination identifier after creation so a later revision updates the intended record instead of creating another copy.
Start with draft-only imports
Send a small test article with representative structures and inspect the resulting preview. Test missing fields, media failure, and an interrupted response. Define which system owns the content after an editor begins making changes in the CMS.
The content remains editable, attribution and taxonomy are intentional, and uncertain writes can be reconciled. Choose a platform guide for the next step rather than copying a request format from another system.
Take the next step
For a worked editorial approach, read WordPress posts API: build a draft-first workflow. Then explore Ghost CMS Write API for the connected part of the workflow.