Start here

Build with GovCMS

Connect your website to published institutional content.

Start buildingYour first API request →API referenceRequests and response shape →WebfrontBuild your public website →

A familiar publishing workflow

Editors manage structured content in Web Manager. Your website fetches published records through the public API and presents them using the institution’s design.

Start with published content.The public API is read-only. Drafts and authoring actions require authenticated platform access.

Your first request

For preview, use https://api.preview.govcms.one. Ask your GovCMS contact for your provisioned site ID.

const api = 'https://api.preview.govcms.one'
const params = new URLSearchParams({
  siteId: process.env.GOVCMS_SITE_ID!,
  type: 'news', page: '1', pageSize: '12',
})
const response = await fetch(
  `${api}/v1/public/institutions/content?${params}`,
)
if (!response.ok) throw new Error('Could not load news')
const { data } = await response.json()
const articles = data.records

Run this on your server. Keep configuration server-side and render records with your own accessible components.

What you can build today

News, pages, publications, leadership and procurement listings.
Category filters, exact slug lookup and paginated results.
Custom Next.js frontends with control over layout and presentation.

See Public content API for the full contract.

Know the boundaries

The public endpoint needs no user token because it returns published content only. Portal and Web Manager routes are authenticated, not public read APIs.

There is no published client SDK or self-service API key flow today. Confirm production integration access with GovCMS.

NextQuickstart →