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.
Use API tokens and public content endpoints for a custom plugin, headless frontend, or proprietary CMS bridge. The dashboard walks through the api token handshake and verifies the content endpoint before anything is queued, so the content endpoint approved content will land on is confirmed up front rather than discovered on the first failed publish.
Once Custom API is connected, the content endpoint is selected per business rather than set globally. Agencies running several Custom API properties can keep each one pointed at its own content endpoint without re-authenticating between publishes.
Approved content keeps its title, slug, excerpt, body, metadata, content endpoint, and scheduling together on the way across, so what appears in Custom API matches what was reviewed instead of a stripped-down copy that needs fixing after the fact.
Custom API credentials stay server-side and scoped to the selected business, never reaching the browser. Publishing runs only through the configured production adapter, and if Custom API rejects a request the item stays queued with the provider error attached so the fix happens once instead of the same post being retried blindly.
Next step
Open the audit, onboarding, or publishing workflow and keep the next action tied to a real business profile.