User Activities

The User Activities API lets you track how users interact with your cidaas-powered applications. Each record can include when the action happened, which user was involved, device and location details, and the activity type.

Reports Changelog User Activity

User Activities API

Change Logs

Event Retention

Why use User Activities

Security auditing

Track user actions for security compliance and investigation.

Troubleshooting

Review historical actions to diagnose login or account issues.

Compliance

Maintain audit logs that support regulatory reporting requirements.

Behavior analysis

Understand how users interact with your applications over time.

What is tracked

Only activities of active customers are tracked. Typical events include:

Account lifecycleCreation and profile modifications

SessionsLogin and logout events

CredentialsPassword changes and resets

DevicesDevice registrations and related events

ACCOUNT_CREATED_WITH_CIDAAS_IDENTITYLOGIN_WITH_CIDAASACCOUNT_MODIFIEDand more

Activity fields

Each activity record includes:

Field	Description
eventType	Type of activity (for example ACCOUNT_CREATED_WITH_CIDAAS_IDENTITY, LOGIN_WITH_CIDAAS)
timeStamp	When the activity occurred (ISO 8601)
sub	User identifier
objectType	Type of object affected (for example users, apps)
objectId	ID of the affected object
deviceInfo	Device details (OS, browser, device type, model)
location	Geographic location (IP, country, city, coordinates)
summary	Human-readable summary of the activity
clientId	Client application that triggered the activity

Who can access what

Admin users

Must be in CIDAAS_ADMINS with ADMIN or SECONDARY_ADMIN. Can access all user activities, including their own.

Regular users

Can only access their own activities. The sub in the request must match the token sub.

Group admins

When requesting activities for another user, the caller and target must share at least one group, and the caller must have GROUP_ADMIN in a shared group.

How to query activities

1

Authenticate

Call the API with a bearer token that matches the access rules above.

2

Filter

Narrow by event type, user, date range, object, or client as needed.

3

Paginate

Use from, size, and descending to page through results.

Use the User Activities API to retrieve activity data with filtering and pagination.

Example request

{
  "eventType": ["ACCOUNT_CREATED_WITH_CIDAAS_IDENTITY", "LOGIN_WITH_CIDAAS"],
  "sub": "89c77e6e-4c49-4dad-b3d9-21a19fcad783",
  "from": 0,
  "size": 10,
  "dateFilter": {
    "from_date": "2023-03-02T11:33:55.515Z",
    "to_date": "2023-04-02T11:33:55.515Z"
  },
  "descending": true
}

Filtering options

You can filter activities by:

• Event type: specific activity types (for example ACCOUNT_MODIFIED, LOGIN_WITH_CIDAAS)
• User: filter by user sub or identifier (email, username)
• Date range: from_date and to_date
• Object type: for example users, apps
• Object ID: a specific object
• Client ID: a specific client application

Common use cases

Security monitoring

Track suspicious login attempts, account modifications, or unusual behavior patterns.

User support

Review activity history to help troubleshoot issues or answer support questions.

Compliance reporting

Generate audit reports showing user actions for compliance requirements.

Analytics

Analyze behavior patterns to improve application experience.

Related documentation

Change Logs

Audit configuration changes: what changed, who changed it, and when.

Event Retention

Configure how long user-activity events are kept before they are removed.

Webhook Management

Receive real-time event notifications in your own systems.

User Activities API

Full OpenAPI reference for querying activities.

Need Support?

Please contact us directly on our support page or reach out to cidaas support at [email protected].