View pricing
Delivery updates & SDKs

Make publishing automation clear, reviewable, and easy to connect.

Agents and customer tools need clear answers, signed updates, and reliable update details so automation can proceed without guessing what happened.

Agent routines
Delivery updates

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 https://customer.example.invalid/webhooks/creavily
X-Creavily-Signature: example_signature

{
  "event": "publish.scheduled",
  "jobId": "job_example",
  "brandId": "brand_example",
  "deliveryAttempt": 1
}
acceptedpreviewedscheduleddelivered
Publishing model

Delivery updates

A publishing submission is accepted, one channel succeeds, another hits a platform limit, and the customer tool receives signed updates that explain both outcomes.

01Post confirmed
02Schedule created
03Channel updated
04Update delivered
05Analytics updated
Delivery updatesDelivery pages should make update behavior clear.Integrations do not only need happy-path examples. They need to know how signatures, delivery history, recovery guidance, progress checks, and clear errors behave when publishing work is delayed or blocked.

Delivery pages should make update behavior clear.

Integrations do not only need happy-path examples. They need to know how signatures, delivery history, recovery guidance, progress checks, and clear errors behave when publishing work is delayed or blocked.

Delivery update scenarioA publishing submission is accepted, one channel succeeds, another hits a platform limit, and the customer tool receives signed updates that explain both outcomes.
Signature
Signed delivery

Each update can be verified before customer tools trust it.

Recovery
Recovery path is visible

Delivery history, failure reasons, and next update timing should be visible.

Structure
Consistent update structure

Updates and clear errors should map cleanly into TypeScript SDK types.

Progress
Progress checks remain available

Connected tools can read publishing progress when a delivery update is delayed or missed.

Product detail

Delivery handling checklist

This page should make the integration resilient before users copy the first code example.

VerifyDelivery signatureReject updates that fail signature checks.
StoreDelivery entryAvoid processing the same delivery twice.
Backup pathCheck publishing progressCheck progress when updates are delayed or blocked.
01Signed updates

Use signed messages and delivery history so customer tools can trust each message.

02Clear update structure

Keep submissions and updates consistent for SDKs, connected tools, and external agent tools.

03Delivery visibility

Track delivery history, failure reasons, and the next update window.

01Signedverified delivery
02Historydelivery history and recovery path
03SDK packageSource TypeScript SDK available
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.

Pricing
Workflow and current availability

Distinguish source tooling from hosted access

The repository contains a TypeScript SDK and MCP implementation. Public package distribution and hosted MCP availability are separate release checkpoints; confirm the supported installation and endpoint before configuring an external client.

How to use it

  1. Use the SDK version matching the Public API contract; do not guess a package name or endpoint.
  2. Verify webhook signatures and retain an idempotent record of handled deliveries. Design for retries and out-of-order updates.
  3. For MCP, confirm the transport, Host and Origin policy, least-privilege credential and an approved preview-confirm-status check.

Know the limits

  • Example event timelines are illustrative, not live customer activity feeds.
  • A local MCP protocol test does not prove hosted access, credential rotation, proxy configuration or a real provider side effect.
Is the SDK only planned?

No. A source TypeScript SDK exists. Confirm how the matching release is distributed before installing outside the repository.

Should a webhook retry create another post?

No. Deduplicate event handling and inspect the existing publishing identity and result.