Bearer API keys
Generate and revoke keys from the authenticated API page. Requests use a Bearer token and return structured JSON responses.
CreatorTool exposes the core publishing workflow through authenticated endpoints on API-enabled plans, using the same connected destinations and plan enforcement as the web application.
CreatorTool keeps the shared campaign understandable and reveals destination-specific choices only for platforms that support them.
Generate and revoke keys from the authenticated API page. Requests use a Bearer token and return structured JSON responses.
Send a file or provide an HTTPS media URL. Uploaded assets are stored in the user media library and return identifiers used by campaign requests.
Retrieve useful connected-account identifiers, platform details, capabilities, health, and profile presentation without exposing backend-only fields.
Build a campaign for one or many connected account IDs, provide media, shared copy, and supported destination options, then publish now or schedule.
Read campaign and target status so an automation can distinguish scheduled, processing, published, draft-uploaded, and failed outcomes.
Retrieve current billing-period limits and usage before creating additional work. The API follows the same account, storage, and publishing enforcement as the app.
Automations do not use a separate publishing system. API-created campaigns enter the same validated scheduling and worker flow used by the web composer, which keeps quota enforcement and destination state consistent.
Compare account, publishing, storage, and API limits before choosing.