Confirm a site's template upgrade
Records that a site now runs the current template. Call it as the last step of an upgrade, after the port is pushed to main and, for a site that is live, deployed to production: it is refused with upgrade_not_live while production runs different code from main. Does not deploy or change any code.
Authorizations
API key in the format: Bearer {api_token}
Headers
Makes this write safe to retry: a repeat with the same key replays the first response instead of creating a second resource. Scoped to the account, remembered for 24 hours; reusing a key with a different payload is an error.
255Path Parameters
The resource ID (e.g., "prod_abc123") or slug (e.g., "my-product")
Response
The site's template status after the upgrade
site_template The framework generation the site runs (vinext, tanstack-start); null for a site created before generations were recorded.
The template commit the site was forked from or last upgraded to; null when it cannot be told.
The generation new sites are forked from.
The template commit new sites are forked from.
A tarball of latest_commit, fetchable with curl.
The site is on an older generation or template commit, or its commit cannot be told.

