Activity API

Activity provides an operational view of authorization traces in the authenticated environment. Use its supported filters and bounded limits to locate decisions, reasons, policy versions, and outcome status. The Console Activity view is a companion for inspecting these records.

Use traces for diagnosis

Start with the authorization or trace ID stored in your own business request ledger. Compare the action, subject, audience, mode, decision, active policy version, reasons, and outcome with the application operation. Confirm actual execution from your business ledger and reconcile its result with the reported outcome.

Use trace retrieval for detailed challenge, review, and proof association. Resume through the original authenticated pending-request flow and apply complete proof binding and consumption checks.

Retention and data handling

Activity is subject to the environment's retention behavior and the endpoint's bounded response. Maintain your business transaction ledger alongside the retained Activity records. Preserve an appropriately minimized review record when a report must outlive trace retention.

Avoid copying subject-linked traces or raw proof material into broad analytics or support systems. Share only the identifiers and sanitized context needed for investigation. Production operation and Privacy describe the operational and data boundaries. The contract below specifies supported filters and response fields.

GET /api/v1/activity

Find recent authorization traces by action, decision or subject for operational diagnosis.

Credential: Server credential.

Inputs: Optional exact action_key, decision and subject_id filters. limit defaults 100 and is bounded to 1-500; no cursor is available.

Effect and retry behavior: Read-only, newest decision first. Use the trace for the policy decision and your application ledger for execution state. Reconcile an absent outcome with that ledger.

Parameters

Name / location	Required	Meaning, type and constraints
`limit` (query)	No	Maximum records requested; default 100. The service bounds it to 1-500. No cursor pagination is exposed. integer default: `100`
`action_key` (query)	No	Optional exact dotted action-key filter. string or null
`decision` (query)	No	Optional exact decision filter, normally allow, challenge, hold or deny. string or null
`subject_id` (query)	No	Subject identifier resolved from your authenticated account mapping. string or null

Responses

HTTP status	Meaning	Body
`200`	Recent authorization traces matching the supplied exact filters, newest decision first.	application/json: Array of `AuthorizationTrace`
`422`	The canonical handler returns a Problem for invalid input; correct the request before retrying.	application/problem+json: `Problem`

Response handling: Wrong environment or overly narrow filters can yield no rows. Never resume an action merely because a list item has an allow decision.

Example

HTTP

GET /api/v1/activity?action_key=payout.destination.change&limit=25

Response excerpt (selected fields) - HTTP 200:

[
  {
    "id": "az_example",
    "subject": "sub_example",
    "action": "payout.destination.change",
    "decision": "challenge",
    "mode": "shadow",
    "outcome": "not_executed"
  }
]