One person's P2P activity over time (admin)
Bucketed counts + notional sums for a single user, for the operator activity chart. user_id is matched on EITHER side (sender, receiver or creator) — the same party test GET /admin/fulfillments uses, so the chart and the list it drills into agree about whose transfer a row is. bucket is day|week|month. Sent/received split by the CHARTED user's role, not the caller's. settled counts only confirmed; cancelled folds cancelled|declined|expired and is returned as its OWN series rather than dropped — climbing cancellations are signal. self_payments defaults to exclude: a self→self fulfillment is funding plumbing, and counting it as customer activity misreads treasury operations as behaviour. Aggregated in SQL, so cost scales with buckets rather than transfers.
Request
- Base URL: https://api.instruxi.dev/api/v1/enforcer
- URL: https://api.instruxi.dev/api/v1/enforcer/admin/fulfillments/timeseries
- Auth: one of:
- API key in header Authorization
- API key in header X-API-Key
Query parameters
the person to chart (either side)
day|week|month (default day)
RFC3339 lower bound (inclusive)
RFC3339 upper bound (exclusive)
sent|received|all (default all)
include|exclude|only (default exclude)
view another tenant (admin only)
Response
OK
Example response
{
"success": true
}Changes
No recorded changes to this operation across all 1 revision of this API.