POST /v1/jobs/{jobId}/artifacts/verify

Computes the SHA-256 of each stored file you name and, when you give an expected_sha256, reports whether they match. Files are hashed one after another. Requires write access to the job, so a project viewer cannot use it.

Each results entry describes one item, in request order, and a problem with one file does not fail the request. A key you cannot read is reported as error: "not_found", the same as a missing file. A file larger than 200 MiB (or the limit the server is configured with) is reported as error: "object-too-large" and not hashed. Items without a string s3_key are dropped, and a request left with no items returns 400.

Add persist=true, as a query parameter or in the body, to also save the results as verification records for the job; read them back with GET /api/v1/jobs/{job_id}/artifacts/list-verifications. A failure to save is not reported in the response.

curl -X POST 'https://ivybiosciences.com/api/v1/jobs/{jobId}/artifacts/verify' \
  -H "Authorization: Bearer $IVY_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
  "items": [
    {
      "s3_key": ""
    }
  ]
}'