Sites Publish API
Multi-site publishing is more than repeating a request. Each destination may have its own audience, path structure, editorial rules, and release authority.
A practical starting point
Maintain a site registry with explicit destination identifiers and supported content types. Attach each delivery job to one site context so configuration from another property cannot silently leak into the release.
Different destinations expect different artifacts. A CMS may accept a record, a static generator may consume content files, and a builder may expose a limited set of supported actions. The guides here focus on field mapping, media, stable destination identities, and release previews. They do not assume that every platform offers the same interface.
Keep the boundary clear
Preview shared updates on representative sites and record outcomes independently. A successful publish to one property does not prove that the whole multi-site release is complete.
Concepts, not a bundled service
This is an editorial guide to Sites Publish API. Evaluate the pattern against your actual destination, permissions, and operating requirements. PublishAPI.com does not provide a live connector, endpoint, or account for this topic.
Turn the idea into a reviewable plan
Choose one representative article with headings, an image, a caption, and internal links. Follow its path into a draft or generated release, inspect the real rendering, and make a correction. Select the WordPress, Hugo, or Ghost guide based on your actual destination rather than attempting to standardize every implementation detail too early.
Continue with WordPress REST API: start with a draft, or compare the related routes below. Keep a record of the decisions that apply to your project rather than assuming a label guarantees a particular capability.