For the complete documentation index, see llms.txt. This page is also available as Markdown.

Monitor a request

Track a request's lifecycle through events or a synchronous getRequest call.

Once a subscription or redemption request is in place, its whole lifecycle can be monitored either by reading the events emitted by the shares contract, or by synchronously querying it.

Asynchronous: events

The key events for tracking a request's lifecycle:

Subscription

Event
Description

SubscriptionRequest

Subscription request created

SubscriptionApproval

Subscription request approved

SubscriptionCancellation

Subscription request cancelled by the user or receiver

SubscriptionDenial

Subscription request denied by a fund operator

SubscriptionRequestExpired

Subscription request expired without action

Redemption

Event
Description

RedemptionRequest

Redemption request created

RedemptionApproval

Redemption request approved

RedemptionCancellation

Redemption request cancelled by the user or receiver

RedemptionDenial

Redemption request denied by a fund operator

RedemptionRequestExpired

Redemption request expired without action

The requestId returned when you create a request is the key to filter on. For example, to capture the id from your own subscription:

Synchronous: getRequest

To query a request's current state directly, pass the requestId:

Last updated