Machine-readable distribution and correction channel for a restricted reference dataset
TCAP content-hash API — current public docs
TCAP's content-hash API is an authenticated interface for onboarded users to obtain content fingerprints with classification and file metadata. Its public documentation describes bulk retrieval, incremental updates and per-hash feedback, including fields that can communicate withdrawal from the reference collection.
Onboarding, withdrawal and feedback
Authentication documentation presupposes an existing onboarded TCAP or Archive account rather than offering unrestricted public access. Hash records include deleted and updated_on fields, with checkpointing to support recipient caches and guidance to monitor deprecated values. Authenticated users can report problems with individual hashes and retrieve their own analyst responses or decisions. Documentation examples are illustrative rather than actual case counts. This interface is distinct from the older URL-alert adapter inspected in Altitude, whose active/inactive field concerns URL availability rather than withdrawn classification.
TCAP content-hash API — current public docs → Onboarded TCAP hash-list recipient
documents withdrawal metadata and incremental update handling
Hash records carry deleted and updated_on fields; checkpointing supports recipient caches and monitoring deprecated values is recommended. This interface can convey withdrawal, but recipient synchronization, erasure or reopening prior restrictions is unobserved. The documented output is withdrawal metadata for a recipient, not a command that restores an account or proof that a recipient applied it.
TCAP Archive and Research Portal → TCAP content-hash API — current public docs
supplies the content fingerprints described by the API
Current public documentation describes bulk fingerprints with classification/file metadata and updates. Media access, restricted database credentials and software licensing remain separate.
TCAP content-hash API — current public docs → TCAP per-hash feedback and analyst response
provides authenticated per-hash error and inclusion feedback
Hash-list users may report individual-hash problems and retrieve their own analyst response/decision. Example counts, names and timestamps are illustrative, not actual cases or volume.
Terrorist Content Analytics Platform → TCAP content-hash API — current public docs
requires prior onboarding for authenticated API use
Authentication introduction presupposes an existing onboarded TCAP or Archive account. It does not publish the current decision-maker, full eligibility contract or unrestricted access.
Current public documentation describes bulk fingerprints with classification/file metadata and updates. Media access, restricted database credentials and software licensing remain separate.
Authentication introduction presupposes an existing onboarded TCAP or Archive account. It does not publish the current decision-maker, full eligibility contract or unrestricted access.
Hash-list users may report individual-hash problems and retrieve their own analyst response/decision. Example counts, names and timestamps are illustrative, not actual cases or volume.
Hash records carry deleted and updated_on fields; checkpointing supports recipient caches and monitoring deprecated values is recommended. This interface can convey withdrawal, but recipient synchronization, erasure or reopening prior restrictions is unobserved. The documented output is withdrawal metadata for a recipient, not a command that restores an account or proof that a recipient applied it.