Docs · API · Schedules

Autonomous schedules.

A schedule is a standing brief: you describe the topic areas and cadence once, and the engine plans each concrete article itself — trend-aware, grounded in the brand profile, and never repeating what it already published. Each run creates a normal article job that debits credits at the standard rate.

Platform capabilityAutonomous mode is a platform-level capability. While it is disabled, creating a schedule or resuming a paused one returns 403 with code autonomous_mode_disabled; existing schedules stay dormant (no runs, no credits burned). Listing, pausing, and deleting always work.

Create a schedule#

POST/v1/schedules

Field	Type		Description
brand_profile_id	string	required	Brand profile the schedule writes for.
instructions	string	required · 10–4000 chars	The standing brief: topic areas, angles, audience. The engine picks each topic itself.
articles_per_month	integer	default 4 · 1–30	Target cadence. Runs are spaced evenly across the month.
mode	"standard" \| "deep_research"	default standard	Pipeline depth per article — 10 vs 25 credits.
require_review	boolean	default true	true: articles wait in your review queue. false: auto-publish when an auto-publish integration is configured on the schedule.

Request

curl -X POST https://scribe.whizztech.ai/v1/schedules \
  -H "Authorization: Bearer $SCRIBE_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "brand_profile_id": "1f4c9a02-7d38-4b06-8f5e-c93a2e61b7d0",
    "instructions": "4 posts a month on fleet electrification and route optimization. Trend-driven angles, mid-market operations audience.",
    "articles_per_month": 4,
    "mode": "standard",
    "require_review": true
  }'

Response · 201 Created

{
  "id": "b7e2a911-4c5f-4f7e-9b3a-8f21d6c07a44",
  "object": "schedule",
  "active": true,
  "brand_profile_id": "1f4c9a02-7d38-4b06-8f5e-c93a2e61b7d0",
  "instructions": "4 posts a month on fleet electrification and route optimization. Trend-driven angles, mid-market operations audience.",
  "articles_per_month": 4,
  "mode": "standard",
  "require_review": true,
  "last_run_at": null,
  "next_run_at": "2026-07-20T00:00:00.000Z",
  "created_at": "2026-07-15T12:00:00.000Z"
}

Response · 403 while autonomous mode is off

{
  "error": {
    "code": "autonomous_mode_disabled",
    "message": "Autonomous mode is not enabled on this platform yet. Existing schedules stay dormant; contact support to get early access."
  }
}

Run cadence#

The first run is deferred to the start of next week — Monday 00:00 UTC.
After each run, the next one is scheduled at monthly-rate spacing: 30 days / articles_per_month.
Each run picks one topic (searching current developments, skipping already-published titles), then creates a standard article job — visible via GET /v1/jobs/{id} and webhooks like any other job.
If the organization has insufficient credits when a run fires, the run is pushed back a day and retried — nothing is charged.

List, retrieve, pause, resume#

GET/v1/schedules

GET/v1/schedules/{id}

PATCH/v1/schedules/{id}

PATCH accepts any of active, instructions, articles_per_month, mode, require_review. Pausing (active: false) is always allowed; resuming requires autonomous mode to be enabled.

Pause a schedule

curl -X PATCH https://scribe.whizztech.ai/v1/schedules/b7e2a911-4c5f-4f7e-9b3a-8f21d6c07a44 \
  -H "Authorization: Bearer $SCRIBE_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "active": false }'

Delete#

DELETE/v1/schedules/{id}

Response · 200 OK

{ "id": "b7e2a911-4c5f-4f7e-9b3a-8f21d6c07a44", "object": "schedule", "deleted": true }

Deleting a schedule never touches articles it already produced — only future runs stop.

NextWebhooks→