Activities

Use this page to read the normalized reporting activity feed across runtime and management behavior.

Who This Is For

operators who need a chronological evidence feed
developers building internal reporting views
teams that want a normalized activity stream instead of raw audit events

When To Use This

Use activities when you want a general reporting feed with filters for product, customer, license, order, subscription, feature, and runtime result context.

If you need raw audit-chain events, use the events API instead. If you need a frozen artifact, use the export API.

How It Works

GET /api/v1/activities uses report:read and supports:

cursor
limit
from
to
action
source
product_id
customer_id
license_id
order_id
subscription_id
feature_code
request_id
result_class
status_code

Response shape:

data: activity rows
page_info.next_cursor
meta

Use the read API for interactive filtering. Use Reporting Exports when you need a frozen artifact.

Example

bash

curl "https://api.licensekit.dev/api/v1/activities?license_id=lic_123&limit=50" \
  -H "Authorization: Bearer $LICENSEKIT_TOKEN"

Typical response envelope:

json

{
  "data": [
    {
      "action": "usage.consumed",
      "license_id": "lic_123",
      "feature_code": "api_calls",
      "status_code": 200
    }
  ],
  "page_info": {
    "next_cursor": 12345
  },
  "meta": {
    "request_id": "req_123"
  }
}

Common Mistakes

confusing activities with the raw audit-backed events feed
expecting the activity feed to be frozen like an export
using event:read instead of report:read

Activities ​

Who This Is For ​

When To Use This ​

How It Works ​

Example ​

Common Mistakes ​

Related Pages ​