Skip to main content
Retrieve daily feature usage summaries by UTC date, product, feature name, event name and license. Summaries contain events recorded with RegisterEvent or RegisterEvents. Use an access token with Usage Analytics permission.

Parameters

This method is accessed by https://api.cryptolens.io/api/ai/GetDailyFeatureUsage. Both GET and POST are supported.

Results

Example Results

Errors

Remarks

  • These summaries describe recorded events, not which features are enabled on a license. Recent events may take several minutes to appear.
  • Dates use the event occurrence time in UTC. Late-arriving events can update earlier daily rows.
  • Row IDs support pagination, not change tracking. Re-query the relevant date range to pick up updated counts; continuing only after the highest previously seen Id will miss changes to existing rows.
  • Use NewestFirst=true to start at the highest row IDs without a cursor. To report recent activity dates, also set Start and End: an older row can receive new events without changing its Id.
  • Keep the same filters while paging. The response is a current page of data, not a fixed snapshot across multiple requests.
  • Events without a product or license remain included when no corresponding filter or access-token restriction excludes them.
  • Historical rows remain available after a product or license is deleted. Explicit product and license filters must identify records still owned by the account.
  • Each row includes KeyId (the global license ID) and Key (the current license string). Key is empty when the license is unassociated or no longer available to the account; historical IDs and counts remain unchanged.
  • Product and license restrictions on the access token apply even when the corresponding request filter is omitted. Invalid or inaccessible references return an error.
  • For a distinct reporting-license total across several days or features, count distinct non-null KeyId values across all relevant rows. EventCount counts events; different event names do not necessarily represent separate uses.
View the original Web API reference