Usage Metrics
Reporting & Analytics
Usage Metrics
GET
Usage Metrics
Retrieve usage metrics and statistics for KYC operations. Track checks, validations, errors, and watchlist activity over time.
Common validation errors:
Endpoint
Authentication
Requiresusage:read permission. Include your Bearer token in the Authorization header.
Query Parameters
Granularity Options
Request Example
Additional Request Examples
Daily Granularity (Specific Month)
Hourly Granularity (Specific Day)
Monthly Granularity (Last 6 Months)
Invalidate Cache
Legacy Format
Response Format
Success Response (Daily Granularity)
Success Response (Hourly Granularity)
Metric fields with zero values are always included in the response for consistent data structure across all time periods.
Success Response (Monthly Granularity)
Legacy Response Format
When usinglegacy=true, the response follows a simplified format for backward compatibility:
The legacy format only returns current month data and a simplified metric set. For detailed metrics and historical data, use the standard response format.
Response Fields
Metric Fields
Each data point contains:Batch Processing Metrics
Adverse Media Metrics
Web Validation Metrics
Crypto Wallet Metrics
Usage Examples
Python Example
JavaScript Example
Error Responses
400 Bad Request - Invalid Parameters
- Invalid date format
- Future dates/months
- Invalid granularity value
- Missing required
dateparameter forhourgranularity monthsout of range (must be 1-12)
403 Forbidden - Missing Permission
403 Forbidden - Missing Tenant
Status Codes
Caching
- Responses are cached for 5 minutes
- Use
cache_bust=trueto force fresh data - Cache headers:
Cache-Control: max-age=300 - With
cache_bust:Cache-Control: no-cache, no-store
Data Characteristics
- Gap Filling: All periods (even with zero activity) are included for continuous charts
- Immutability: Historical data never changes, so responses are cacheable
- Real-time: Current day/hour data updates as requests are processed
- Retention: Metrics are retained for at least 12 months