Knowledge Hub now has a public REST API

Starting today, the Knowledge Hub has a public REST API. You can create and edit pages, ingest sources from URLs, and list and organize folders, all through the same workspace API keys you already use for the rest of the Exec API.

Customers keep building more of their training workflow around the Knowledge Hub. Enablement teams write coaching pages alongside roleplay scenarios, attach reference materials as sources, and keep it all organized in folders. That work has happened by hand in the browser. If you wanted to sync a page from your internal wiki or push a batch of reference links into a hub, you had to do it one at a time.

Now you can script it. The API exposes three resource types. Pages support GET, POST, PATCH, and DELETE, and every write goes through the same draft-to-publish version flow you see in the UI. Sources support GET, POST, and DELETE, and creating one from a URL kicks off content extraction automatically. Folders support GET so you can navigate the hierarchy and filter by folder, owner, or skill across resources.

If your team already syncs content from Notion, Guru, or Google Drive into the Knowledge Hub, you can now automate that from your side instead of relying on manual uploads. If you generate coaching content programmatically, you can push it straight into a draft page and publish when it's ready. If you want to keep your skill taxonomy consistent across systems, you can filter and pull pages by linked skill.

The API includes pagination on list endpoints, include flags for draft content and extracted source text, and a full OpenAPI specification so you can generate a client in whatever language your stack runs. Authentication is the same Bearer token model the rest of the Exec API uses.

We built this because customers told us the Knowledge Hub was becoming the place where their coaching knowledge actually lived, not just a bucket of attached files. When your knowledge base is central to how reps prepare and how scenarios get their context, you need programmatic access to keep it current. Programmatic access lets you keep dozens or hundreds of pages and sources accurate without touching each one by hand.

The endpoints are live now. You'll find the base URL, key format, and full request and response shapes in the API documentation. If you're building something against it and hit a wall, tell us. We want to know what you're wiring up.