AckPost
Developer docs
Build publishing workflows without bypassing approvals.
AckPost is being built for agent-assisted publishing, but programmable workflows still need brand controls, approval gates, destination checks, and proof records.
MCP tools
Use AckPost from agent workflows to list articles, create drafts, schedule content, generate social blasts, and create article images where enabled.
View sectionPublishing workflow
Create content, map destinations, request approval, schedule jobs, and keep proof history attached to publishing events.
View sectionMigration
Import scheduled content from CSV exports and map rows into brands, destinations, drafts, or queue entries.
View sectionSecurity
Understand OAuth access, token handling, approval gates, and audit history before connecting accounts.
View sectionDeveloper principles
- Agent-created content should still pass through brand, approval, and destination checks.
- Automations should preserve source context, including source article and target destination.
- REST endpoints will be documented publicly as they graduate from internal product APIs.
- MCP is the current developer entry point for agent-assisted AckPost workflows.