What Can I Do with the Content Hub API?

Updated

The Content Hub API gives you a fast, flexible way to read and modify the content you store in Content Hub and to connect that content to your existing workflows. It is available on the Starter, Pro, and Ultimate plans; the Basic plan does not include API access. If you only need to schedule posts through the Content Hub interface, the API is optional. If you want your content to move automatically between Content Hub and other tools, it is the part of the product you will build on.

What the API is for

Content Hub describes content ownership and ease of use as its primary drivers, and the API exists so that your content is never locked inside the platform. In practice, that means two things:

  • Access — you can pull your content out of Content Hub programmatically instead of copying it by hand.
  • Modification — you can update content through the API and keep it in sync with whatever else you use.

Because the API is described as a way to "interact with your content and integrate it with all your workflows," it is best understood as a connector rather than a separate feature. The value comes from what you attach it to.

Practical things you can build

The page evidence does not list individual endpoints, so the examples below are task patterns rather than documented calls. Each one maps to a capability Content Hub already exposes in its interface.

Sync content into a site or app

Content Hub supports placing your news on your own website using placeholders such as #title#, #description#, and #publishdate#. An API integration is the natural next step when you want that content rendered dynamically — for example, feeding a custom front end, a static site build, or a mobile app from the same content you publish elsewhere.

Feed content into other tools

If your team already works in a CMS, a data warehouse, or an internal dashboard, the API lets you push Content Hub content into those systems instead of re-entering it. This is the "integrate it with all your workflows" use case: one source of content, many destinations.

Automate versioning and scheduling

Content Hub lets a single piece of content have multiple versions and metadata — for example, shorter text for Twitter and a different image for a Facebook post — and lets you schedule each version to different outlets. An API integration can generate or update those versions programmatically, which is useful when the same content needs to appear in several formats on a recurring basis.

Pull performance data alongside your content

Content Hub tracks any KPI its crawler can access, such as Facebook likes, Twitter followers, app downloads, or revenue. If you want those numbers in your own reporting stack rather than only inside Content Hub, an API-based pull is the way to combine content and results in one place.

What you need before you start

  • A paid plan. API access starts at Starter ($19 per month, 3 projects, 3 users, 10 aggregation sources, 6 KPIs). Pro ($79 per month) and Ultimate ($149 per month) include it as well. Basic is free forever but has no API.
  • Content already in Content Hub. The API operates on your content, so the aggregation sources, versions, and metadata need to exist first.
  • A destination. Decide up front whether you are reading content out, writing updates in, or both — that determines how much of your workflow you are replacing.

How to approach an integration

  1. Confirm your plan includes the API. Check the pricing tier you are on; if you are on Basic, the API is not available.
  2. Set up the content you want to work with. Add aggregation sources and create the versions and metadata you intend to sync.
  3. Choose one workflow to connect first. A single destination — your website, a CMS, or a reporting tool — is easier to validate than several at once.
  4. Verify against the interface. After a sync runs, compare what arrived at the destination with what Content Hub shows. Because the API is meant to keep content accessible and modifiable, anything you can see and edit in Content Hub should be reachable through the integration.
  5. Expand once it is stable. Add more destinations or automate version creation only after the first connection behaves predictably.

Common sticking points

  • Assuming the API is on every plan. It is not. Basic excludes it, so an integration built on a free account will not work.
  • Treating the API as a publishing shortcut. It connects your content to workflows; scheduling to Facebook, Twitter, and LinkedIn is already handled inside Content Hub and does not require the API.
  • Skipping the version model. Content Hub is built around multiple versions and metadata per piece of content. An integration that assumes one format per item will fight the platform's design.
  • Forgetting ownership. The stated goal is that it is always easy for you to access and modify your content. If an integration makes your content harder to reach, it is working against the reason the API exists.

If your goal is simply to write, schedule, and track posts, the built-in calendar and KPI tracking cover it. Reach for the API when content needs to live in more than one system at once.