POST
Retry a forensics run
Request · Response · Guide: fileForensics
Returns a NEW run_id in the same shape as the create response; poll that one. The original run stays queryable and reports status error.Use this for a run stuck in queued or running for more than ~6 minutes, or one that ended in error.

Authorizations

​
x-api-key
string
header
required

API key for authentication

Path Parameters

​
run_id
string
required

The run to retry.

Response

Retry accepted and queued under a new run_id.

​
run_id
string
required
Example:

"eebb50fee5b1"

​
file_id
string
required
​
spec_filter
enum<string>[]
required
Available options:
web_presence,
ai_gen_detection,
ai_text_detection,
copy_move,
exact_duplicate,
provenance_credentials,
generation_toolchain,
producer_divergence,
encryption_permissions,
active_content,
digital_signature,
attachments,
revision_history,
magic_byte,
polyglot,
trailing_data,
entropy,
ai_pdf_detection,
ai_office_detection,
heatmap,
document_integrity_decisions,
layout_parse
Example:
​
status
enum<string>
required
Available options:
queued
Example:

"queued"

​
poll_url
string<uri-reference>
required

URL of GET /v1/forensics/runs/{run_id}.

​
created_at
string<date-time>
required