Weekly listing reel on a Sume schedule: the $1.00 default cap

A weekly listing reel can run on a Sume schedule, but two facts decide whether it works for you. A schedule with no generation spend cap set runs with a default of $1.00, and the schedule itself can only be created in the dashboard. The Developer API can list, read, start and monitor scheduled runs, and it has no write endpoints for creating or editing them. If your reel needs more than one dollar of generation, set the cap on the schedule first.

What the Actions API exposes

The scheduled-run docs describe the namespace as /v1/actions with ids that start with aut_. A schedule is started either by its cron or by POST /v1/actions/{action_id}/runs, and the second route works only when api_trigger_enabled is true. Both choices are fixed when the schedule is created.

Steps

Treat the schedule like a standing order and the API like the way to inspect it.

• In the dashboard, create the schedule with the instructions for the reel and set the spend cap deliberately, since the default is only $1.00.
• Decide at creation whether the schedule needs the API trigger as well as cron, because that choice does not change later.
• Use GET /v1/actions to find the aut_ id and confirm api_trigger_enabled before you call the run endpoint.
• Start a one-off run with POST /v1/actions/{action_id}/runs using a key that carries actions:write, and attach an Idempotency-Key so a retry does not start two runs.

What Sume does not do

Sume does not let a script create or change the schedule, and a service-account key cannot call these routes at all, so a CI job needs a user key with the right scope. The run has no events_url phase timeline, so progress is read from the run itself or from a run webhook.

A reel is also not automatically a finished post. The schedule produces files in a thread; getting them onto a listing page or a social account is a separate step that you wire. For the Format-based alternative, where the API creates every run directly, see the weekly series post linked below.

One more planning point: because the cap can only be lowered per run, a cap that is too low at creation will block a heavier week, such as the run-up to a sale, and you would have to edit the schedule in the dashboard. Decide the cap from your heaviest planned week, then lower it per run for lighter ones through the run request, and watch the spend on the run receipt after the first scheduled week before you trust the number.