Recommended setup
Custom API uses api token as the recommended way to connect and publish approved content.
Integration guide
Use API tokens and public content endpoints for a custom plugin, headless frontend, or proprietary CMS bridge.
API token
Auth
Draft/live
Modes
Queue
Runtime
Use API tokens and public content endpoints for a custom plugin, headless frontend, or proprietary CMS bridge.
Custom API uses api token as the recommended way to connect and publish approved content.
Connection credentials are protected while the dashboard shows verification, publishing status, and any action needed from your team.
Provider credentials remain server-side, access is scoped to the selected business, and publishing is only attempted through the configured production adapter.
Approved content keeps its title, slug, excerpt, body, metadata, destination, and scheduling details together throughout publishing.
Next step
Open the audit, onboarding, or publishing workflow and keep the next action tied to a real business profile.