Skip to content

Blocked Autograph Tags Resource ​

Description ​

The Blocked Autograph Tags resource is a sub-resource of the Antifraud statistics resource. It lets you manage end-users/tags that are currently blocked by the anti-fraud system.

When a suspected fraudulent end-user (or tag) is blocked, its corresponding record in the antifraud database gets a blocked_at marker, and all video links tagged with the corresponding autograph_tag stop working (streaming/downloading is denied). A block can happen for one of two reasons:

  • join_fraud — the determined fraud score of the end-user exceeded the application's configured block_threshold (suspected sign-up fraud). This can also happen "inherited": when a new tag is joined with the same email address as an already blocked tag.
  • piracy — the tag was identified as the source of a pirated copy of your video through the backtracing feature.

This resource allows you to:

  • List all currently blocked tags across your applications, including the reason (cause) for each block.
  • Fetch the blocked records of a specific tag.
  • Unblock a tag again (e.g. when a block turns out to be a false positive).

Supported Methods ​

GET /stats/antifraud/blocked_tags/ ​

List all blocked tags, optionally filtered by application, block cause, time range, or a single tag. Results are sorted by blocked_at (newest first) by default.

For detailed information, see GET /stats/antifraud/blocked_tags/.

GET /stats/antifraud/blocked_tags/ ​

Fetch the blocked records of a specific tag across your applications, honoring the same query-parameter filters as the list endpoint.

For detailed information, see GET /stats/antifraud/blocked_tags/.

DELETE /stats/antifraud/blocked_tags/ ​

Unblock a specific tag. Without additional filters, all matching blocked records for the tag across your applications are unblocked; with application.id and/or cause filters, only the matching records are unblocked.

For detailed information, see DELETE /stats/antifraud/blocked_tags/{tag}.

Authentication ​

All endpoints require a Bearer token for authentication.