Get Time to Detection
How long threats were already live before the earliest automated detection of the asset, for any organization. Broken down by asset type, for distinct assets this organization blocked in the date range that are still blocked today. The clock runs from when the asset was first seen live to its earliest automated detection; a human report does not stop it. Each median is a minimum.
Overview
Get how long threats were already live before ChainPatrol’s automation first detected them, per asset type. It covers the distinct assets your organization blocked in a date range that are still blocked today.time-to-detection-chart feature flag on a
per-organization basis. If the flag is not enabled for your organization, the API
returns a 403 Forbidden error. Contact ChainPatrol to enable access.Request Body
How it is measured
The clock runs from the first time anyone saw the asset live to its earliest automated detection, for any organization. A human report does not stop the clock, including your own.byAssetType has one entry per asset type, most blocks first:
Authorizations
Your API key. This is required by most endpoints to access our API programatically. Reach out to us at support@chainpatrol.io to get an API key for your use.
Body
Organization slug
1Only include assets blocked on or after this date. A date-only value (YYYY-MM-DD) starts at midnight UTC
Only include assets blocked on or before this date. A date-only value (YYYY-MM-DD) covers the whole day in UTC; pass a full timestamp for a precise cut-off
Only include assets belonging to these brands
x > 0Only include assets scanned from these ISO 3166-1 alpha-2 countries
2Response
Successful response
Time to Detection, one entry per asset type this organization blocked in the range, descending by number blocked. The clock stops at the earliest automated detection of the asset for any organization, not at this organization's report. Assets that do not enter withEvidence are left out of the median. For URL and page assets only an observed-serving date counts, so a domain registration date never enters the number