Retrieves activity logs for the specified account with optional filtering and pagination.

post

https://bench.gobridgit.com/rp/api/v1/accounts/{accountId}/activities/_filter

This endpoint returns a paginated list of activities that occurred within the account. The results can be filtered by:

Person IDs (maximum 10)
Project IDs (maximum 10)
Date range (happenedFrom and happenedTo)
User IDs who triggered the events (maximum 10)
Activity types (maximum 25)

Note: Either PersonIds or ProjectIds can be specified, but not both simultaneously.

The response includes a query-has-more header indicating whether additional records are available beyond the current page.
Permissions
Private: Read
Finance: Read
Person: Read
HourlyProfile: Read
Project: Read
Communication: Read
Role: Read
HourlyRole: Read
Allocation: Read
HourlyAllocation: Read
Settings: Read

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

accountId

int32

required

The account ID (must be greater than zero)

Body Params

The filter criteria containing:

offset: Starting position for pagination (default: 0, must be non-negative)
limit: Maximum number of records to return (default: 25, range: 1-50)
predicates: Optional filtering predicates including:
- personIds: Array of person IDs to filter by (max 50 items)
- projectIds: Array of project IDs to filter by (max 10 items)
- happenedFrom: Start date for filtering events (optional, range: 1900-01-01 to 2100-01-01)
- happenedTo: End date for filtering events (optional, range: 1900-01-01 to 2100-01-01, must be after happenedFrom if both provided)
- triggeredByUserIds: Array of user IDs who triggered the events (max 10 items)
- activityTypes: Array of activity type strings (max 25 items)
- triggeredByIntegrations: Boolean to include activities triggered by integrations (default: true)
- triggeredByUsers: Boolean to include activities triggered by users (default: true)
- groupingIds: Array of grouping IDs to filter by

offset

int32

required

limit

int32

required

1 to 50

predicates

object

Headers

content-type

string

enum

Defaults to application/json-patch+json

Generated from available request content types

Allowed:

Responses

400

Bad Request - Invalid filter parameters or validation errors (e.g., invalid date range, too many filter values, invalid activity type format)

401

Unauthorized - Authentication token is missing or invalid

403

Forbidden - User does not have required permissions or account access

200Successfully retrieved the activity logs. The response includes a query-has-more header indicating if more records are available.