Agency Black Friday: a team-owned Format needs a workspace key

A personal API key cannot run a Format that a team workspace owns. Sume answers 403 workspace_key_required, so issue the key inside the team before launch.

3 min readSume
All posts

If a team workspace owns the Format, a personal key will not work. The error is 403 workspace_key_required, and details.workspace_id names the workspace whose key you need.

Three key problems that look alike

403 causes on Format runs (Sume docs, read 2026-10-05)
SymptomCauseFix
403 insufficient_scopeKey lacks formats:write or formats:readMint a new key; scopes cannot be added
403 insufficient_scope with service_account_format_runs_unsupportedService-account keyUse a user key
403 workspace_key_requiredPersonal key, team FormatCreate the key in the team workspace

What stays the same

The Format address, the body and the bulk endpoint are unchanged. The run, its media and its spend belong to the key that made the call, and team runs count against the team's generation concurrency. For an agency, that means one key per client workspace, kept on your server, not one shared key.

Before launch day

  • Create the keys a week early and run one tiny call per client.
  • Check the GET /v1/formats list for each key: a Format outside the key's workspace answers 404 format_not_found, which can look like a typo.
  • Do not ship these keys to a browser.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume