Kapost
Kapost is a content operations platform — now part of Upland Software — that lets B2B marketing teams plan, produce, distribute, and analyze content across the customer journey through its Canvas, Studio, Gallery, and Insights modules. Kapost exposes a versioned REST Content API (/api/v1) secured with HTTP Basic authentication using a per-user API token and returning JSON, plus outbound content webhooks (create/update/publish/delete), an XML-RPC interface, and a first-party WordPress plugin for publishing content from Kapost to WordPress sites. This profile was enriched from Kapost's live developer portal.
Kapost publishes 1 API on the APIs.io network. Tagged areas include Content Operations, Content Marketing, Content Management, Marketing, and Sales Enablement.
The Kapost catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Kapost’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, authentication, and 8 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Kapost Content API
Versioned REST Content API for managing content, collections, ideas, initiatives, custom fields, tasks, users, and insights. HTTP Basic auth with a per-user API token (password ...
Event Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Kapost Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 2
The organization behind the API