Published Post Delivery

The content API serves only published posts, exposing titles, bodies, and feature images to any application with a valid content key. A Beam agent reads this feed on a schedule or webhook, checks it against the customer's approved rule, for example that any post tagged for a specific site section should appear in a linked directory, and updates that destination with the new entry. It never touches draft or scheduled posts, since the content API cannot see them at all. Anything involving how a post should be worded or categorized before it goes out is routed to a human editor working on the admin side.

Tag and Author Filtering

Every published post carries tags and author fields that the content API returns alongside the body text. A Beam agent filters this feed for the tags or authors the customer cares about, for example gathering only posts tagged for a newsletter, and applies the approved rule, such as adding the matching entries to a digest document or an internal list. It draws solely on the fields Ghost returns, nothing else. Anything involving a missing tag, an ambiguous author credit, or a post that seems miscategorized is routed to a human editor to correct at the source, since the agent cannot edit posts through this API.

Read-Only Public Access

The content API is scoped for public, read-only access, so it can sit behind a website or app without exposing the admin side. A Beam agent uses this key to check for new published posts and applies the approved rule, for example notifying a marketing channel when a post in a given tag goes live, or adding it to a content calendar. It cannot draft, edit, or unpublish anything through this key, by design. Anything that requires changing the post itself, such as fixing an error a reader flagged, is routed to a human with admin access, since this key alone allows no writes.