Format vanity URL or skl_ invoke_url: store the opaque path

Which Format URL should you save in your code? Store invoke_url, the opaque skl_ path, because it stays the same after a rename. The vanity URL (handle/slug) reads better in logs, and renamed handles continue to resolve for 90 days.

Series teams rename Formats often: 'episode-pack' becomes 'season-2-pack'. A hard-coded vanity path is the thing that breaks on a Tuesday.

Two addresses, one Format

GET /v1/formats lists the Formats your key's workspace owns plus the first-party catalog. Each entry carries both addresses.

Who sees what

The key sets visibility. A personal key lists personal Formats; a team key lists the Formats of that workspace. A Format outside your key's workspace answers 404 format_not_found, the same as an id that does not exist, so a missing Format usually means you hold the other key. Team Formats need a key created in that workspace.

Formats by Sume answer at the reserved sume handle, and the run, its media and its spend belong to the key that called.

Version pinning

Sume bumps a Format's version on every edit, and the run receipt shows format.version. Log it with every episode so you can tell which recipe made which video.

Migration advice

If you already store vanity URLs, add the opaque path next to each one now. The vanity form is friendlier in a call sheet; the skl_ path is the stable address in code. After a rename, the old handle resolves for 90 days, so you have a window, but it is a deadline and not a guarantee.

• Store invoke_url in config, not the vanity URL.
• Show the vanity URL to humans.
• Check for renamed handles before the 90 days run out.