Create publishing previews, review progress, list media, and schedule confirmed work.
CreavilyBrand publishing
Developer access
APIs, delivery updates, and app connections for social publishing automation.
Creavily gives agents the pieces they need while preserving publishing controls: saved media, publishing previews, limited agent keys, duplicate-protected publishing, and signed updates.
API setup
Automation needs clear submissions and clear delivery updates.
Developers should be able to preview writes, avoid duplicate work, and receive signed updates without digging through setup screens.
POST /v1/public/publishing/batches/preview
Authorization: Bearer $CREAVILY_API_KEY
{
"brandId": "brand_example",
"policy": { "slots": [{ "id": "morning", "localTime": "09:00" }] },
"items": [{
"clientAssetId": "asset_example",
"productId": "product_example",
"text": "Launch caption",
"targets": [{ "platform": "instagram_business", "channelAccountId": "account_example" }]
}]
}acceptedpreviewedscheduleddelivered
Send asset, schedule, publishing, analytics, and automation updates to customer tools.
Let customer tools connect without sharing dashboard sessions or social account access.
Publishing model
Developer path
A customer's automation creates an agent key, imports media, sends a preview submission, then listens for signed updates before enabling live scheduling.
Developer accessDeveloper pages should make integration setup clear.The page needs to explain how a connected tool signs in, submits media-aware publishing work, receives predictable updates, and checks publishing progress. This is how Creavily becomes useful to customer agents.
Developer pages should make integration setup clear.
The page needs to explain how a connected tool signs in, submits media-aware publishing work, receives predictable updates, and checks publishing progress. This is how Creavily becomes useful to customer agents.
Integration scenarioA customer's automation creates an agent key, imports media, sends a preview submission, then listens for signed updates before enabling live scheduling.
REST
Clear API guideDevelopers should see which product areas cover media, channels, posts, brands, and analytics.
OpenAPI
API docs for connected toolsOpenAPI helps SDKs, connected tools, and agents understand submissions and updates.
Access
Limited access by defaultAgent keys should include only the permissions needed by that connected tool.
Lifecycle
Repeat behavior is clearDuplicate protection and progress checks keep automation from creating duplicate work.
Product detail
Developer quick path
A strong developer page shows how to go from first submission to reliable production integration.
1Create agent keyLimit it to read, preview, schedule, or update actions.
2Send previewCheck media and social destinations before writes.
3Subscribe updatesUse signed delivery updates for published-result updates.
Next step
Bring this publishing path into your Creavily workspace.
Use Google login for the human workspace, then connect channels and agent routines when the account is ready.
Integrate against the Public API contract
The Public API is the external business and security boundary. Use the published contract and your granted scopes rather than reproducing internal dashboard requests.
How to use it
- Read OpenAPI, establish a scoped credential and list authorized brand context.
- Prepare authorized media and preview publishing work. Treat validation and write-control failures as explicit outcomes.
- Submit only the confirmed action using its idempotency contract, then inspect delivery state or verify incoming webhooks.
Know the limits
- Organization authority comes from the authenticated principal, not a trusted client-supplied organization identifier.
- Do not log bearer credentials, signed media URLs or raw provider errors. Use safe request identifiers when contacting support.
Are dashboard routes a stable integration API?
No. Customer integrations should use the Public API and SDK contracts, not browser-session routes.
Can preview fail without publishing?
Yes. Readiness and preview failures are part of the safety workflow and never authorize bypassing validation.