04 Mint Signed URLs

Step 4: Mint signed URLs

The fast path creates and generates the artifact for you, but it does not pre-mint download URLs โ€” mint them the same way as the on-demand path once the artifact is completed: POST /artifacts/{{af_artifact_id}}/signed-urls.

What this step does & why it's needed

Identical to the on-demand mint step: it exchanges the artifact id for short-lived download URLs plus a dashboard link. Even though the fast path built the artifact automatically, download links are never pre-minted โ€” they are an audited, separately-scoped action (artifacts:sign) so that creating an artifact never implicitly hands out access to its bytes. This step is where a caller with signing rights actually pulls the data.

Why you might not need this step

If you set signed_url_ttl_seconds in Step 1, a ready-to-open artifact_dashboard_url was already handed back on the task read in Step 2 โ€” for a human who just needs to view the result, that link is enough and you can skip this call. Use this explicit mint when you need programmatic file downloads (into DuckDB / a pipeline) or want to control the TTL per download.

  • data.attributes.files[] โ€” one signed URL per file. First captured into {{af_signed_url}}.
  • links.dashboard_url โ€” dashboard deep link (also captured into {{af_dashboard_url}}).

Shortcut: if you passed signed_url_ttl_seconds in Step 1, the task read in Step 2 already surfaced artifact_dashboard_url โ€” you can open that directly without this call. This step is the explicit mint for programmatic downloads.

Visualize tab. This step renders the minted URLs as clickable links โ€” open the response Visualize tab to click "Open in Epoch dashboard" or download a file directly, rather than copying a raw string.

Requires the artifacts:sign scope. This is the end of the fast-path workflow โ€” feed {{af_signed_url}} into DuckDB / GeoPandas / QGIS per the consuming recipes.