Sume schedule slug rules: 2-64 characters, and runs is reserved

A schedule slug is lowercase letters and digits with single hyphens as separators. It is 2 to 64 characters and unique within your account, and runs is reserved because it is the next path segment of the run endpoint (API trigger). With a slug you can call a schedule at /v1/actions/{handle}/{slug}/runs instead of the opaque aut_ path.

Quick checks

A schedule made before slugs existed has slug: null. Call it by its aut_ id.

Which path to store

Both paths run the same pipeline, and action.id in the receipt is always the opaque id. Store aut_... in your own system. A renamed handle or slug changes the vanity path, and an old handle resolves for 90 days as a migration window, not a guarantee.

curl -sS -X POST "https://api.sume.com/v1/actions/acme/weekly-teaser/runs" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: weekly-teaser-2026-w41" \
  -d '{}'