{"version":"2.1.234","anchor":"per-asset-delete-route-for-artifacts","canonical_anchor":"per-asset-delete-route-for-artifacts","heading":"Per-asset delete route for artifacts","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/per-asset-delete-route-for-artifacts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Per-asset delete route for artifacts\n\nArtifact assets can now be deleted one at a time through a new route.\n\n**What**\n\nArtifact assets can be deleted individually through a new route built per artifact and asset id, alongside the existing upload and list routes.\n\n**Details**\n\n- The route helper validates the artifact slug and the asset id before calling, and reports through an `artifact_asset_delete` mark with codes including \"invalid_slug\", \"invalid_id\", \"not_writer\", \"policy_denied\" and \"malformed_reply\".\n- The helper itself is unconditional; the asset API as a whole has no separate flag visible in the build.\n\n**Evidence**\n\n`artifact_asset_delete`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}