04 List Signed URL Audit

Step 4: List the signed-URL audit history

Every successful mint is recorded โ€” one row per call. GET /artifacts/{{ad_artifact_id}}/signed-urls returns that history (the URLs themselves are never stored, only the metadata: who minted, when, the TTL, and how many files were covered).

What this step does

It returns the audit trail of every minting event for this artifact โ€” not new URLs. Each row answers "who created a download link, when, for how long, and covering how many files".

Why it's needed

Signed URLs grant direct access to the exported data, so who minted them and when is a security- and compliance-relevant fact. This endpoint is how you review that access after the fact โ€” e.g. to confirm only expected identities pulled a regulatory bundle, or to investigate an unexpected download. Reading the log needs only artifacts:read, so an auditor can see minting activity without being able to mint (artifacts:sign) themselves โ€” the split is intentional.

Why you might skip it

This step is optional โ€” a pure integration that just needs the file can stop after Step 3. Include it when access to the export must be auditable (regulatory packs, shared bundles) or when you're building a UI/report over minting activity.

Response (200)

FieldNotes
attributes.requested_by_user_idThe user who minted; null when minted by an org key.
attributes.ttl_secondsTTL requested at minting.
attributes.issued_at / expires_atWhen the URLs were minted and when they expire.
attributes.partition_countNumber of files covered (equals storage_objects.length at signing).

Visible with artifacts:read; only artifacts:sign can mint (Step 3). This is the end of the on-demand workflow โ€” the same artifact can be re-minted any number of times as TTLs expire.