Renamed a Format handle? Old URLs work for 90 days: store invoke_url

If you rename a Sume Format's handle or slug, the old address keeps resolving for 90 days, according to the Format API docs. After that it is a 404 format_not_found. The fix that never expires is to store the invoke_url from the Format listing, which is the opaque skl_ path and is permanent across renames.

Two addresses, one Format

GET /v1/formats returns both addresses for each Format. The receipt of any run carries the opaque format.id whichever one you used.

What to store

Save invoke_url next to your own record of the Format, and call that. Keep the vanity address only for people to read. If you already stored vanity addresses, run GET /v1/formats once, match on handle and slug while the old address still works, and write the invoke_url back.

A Format you do not own can be renamed by its owner without telling you. A team Format shared with your workspace is called at the owner's address with your own team key, so a rename on their side is a risk for you too; ask the owner to announce renames.

• Persist invoke_url (skl_…) as the key.
• Alert on 404 format_not_found from an address that used to work.
• Remember the same 404 also means archived, or a grant that was removed.

A migration checklist

Do the migration before a rename, not after. List your Formats, store each invoke_url next to your own id, and switch your callers to it. After that, a rename by the owner changes only what people read in the dashboard. Keep one monitor that calls each stored address with a read request, GET /v1/formats/{handle}/{slug} or the opaque equivalent, so you hear about a break before a customer does.

Limits

The 90 days start at the rename, and the docs do not describe a reminder. A 404 does not tell you which cause applies: unknown, archived, outside your key's workspace, or no longer shared all look the same on purpose. Handles of the ready-made catalog live at sume.