generate run, adapting only what the customer’s upload changed. Because every
successful generate writes a fresh recipe, that “latest” naturally drifts.
Pinning fixes the starting point to one known-good run’s recipe. Pinned runs read
it read-only — they don’t promote their adapted recipe back to “latest” — so one
customer’s run can’t move the baseline other runs build on. See
Reuse and pinning.
{source} is the source name (URL-encode it if it contains spaces).
Authentication
Requires anx-api-key header. See Authentication.
Request body
The run whose recipe to pin as this source’s reuse recipe. The run must belong
to your account and have produced a usable recipe (a
generate or update run
that reached a preview or executed). Pass null to unpin and return to
“latest working recipe” drift.Response
200 OK
pinned_recipe_run_id comes back null.
Errors
Example
Next
- Core concepts → Reuse and pinning
- Start a run — what produces a recipe to pin.