BizEvent Resource
Event notice recording and retrieval
BizEvent records business event notices for deposit, redemption, and conversion operations. Events track pending operations before they become BizTransactions.
5
Endpoints
3
Notice Types
5
Operations
7
Filter Fields
Usage Notes
When
- Record event notices for pending deposits, redemptions, and conversions
- Query event history for workflow tracking
- Cancel pending events before processing
Requirements
- Valid Bearer token with event permissions
Notes
- Event notices precede actual transactions (pending state)
- NoticeOfConversion creates TWO linked event records
- Events can be cancelled via PUT /BizEvent/Cancel
Available Endpoints
Event Management
Event Creation
Core Data Transfer Objects
Filter Data Transfer Objects
GET endpoint uses a filter class to bind query parameters. This is a request-only structure for filtering and pagination.
Request & Response Patterns
Identifier Patterns
- Dual identifiers supported: Native 7G IDs (ProductID, AccountID, InvestmentID) and external IDs (externalProductId, externalAccountId, externalInvestmentId)
- Either native or external identifier required for product, account, and investment references
- BizEventID is the unique identifier for event records returned by the API (
longin the SDK; mirrored on the filter asFilterField<long?>)
Multi-Record Operations
- NoticeOfConversion returns 2 linked event records: source investment redemption and target investment allotment
- NoticeOfDeposit and NoticeOfRedemption return single event records
- GET endpoint returns paginated arrays of event records with filtering support
Filtering Capabilities
- GET /BizEvent supports FilterField dot operators for BizEventID, AccountID, ExternalAccountId, BizEventTypeID, AccountNumber
- Direct filtering available via either ProductID or ExternalProductId (alternative identifiers for the same product)
- Standard pagination via PageSize and PageNumber parameters