- keep a fund directory current across managers
- refresh latest NAV or snapshot data in a product or internal workflow
- detect new disclosures and holdings updates
- trigger downstream notifications or review flows when a tracked fund changes
What Rangler gives you
The fund workflow package is built from:GET /v1/fundsGET /v1/funds/{fund_id}GET /v1/funds/{fund_id}/snapshotsGET /v1/funds/{fund_id}/eventsGET /v1/events?type=fund.snapshot.updated&type=fund.disclosure.updated- webhook subscriptions filtered to
fund.snapshot.updatedandfund.disclosure.updated
Start with webhooks
Start with webhooks when fund updates should drive a customer-facing product, internal alert, or review workflow.Directory sync
Fetch the latest fund directory:Latest NAV refresh
Fetch one fund with its latest snapshot:latest_snapshotlatest_holdings_snapshotlatest_snapshot.as_of_datelatest_snapshot.price
ranglerpy:
Latest disclosure update
Fetch historical snapshots for one fund:ranglerpy:
Check the event feed for missed deliveries
ranglerpy for backfills and missed-delivery checks:
Recommended rule
In the portal:- Create a webhook endpoint
- Choose the Fund monitoring preset
- Keep event types:
fund.snapshot.updatedfund.disclosure.updated
- Add fund IDs if you want a narrowed rule
- Leave company IDs empty
Example webhook payload usage
Receiver flow:- verifies the Rangler signature
- checks the event type
- stores
event.idin a durable inbox for duplicate-delivery protection - fetches additional fund detail if needed
- updates downstream state or sends a human alert
ranglerpy helpers.
Top-holdings change monitoring
Rangler does not yet ship a dedicated “holdings diff” event type. For now:- receive or read
fund.disclosure.updated - fetch the latest snapshot
- compare
top_holdingsor holdings-derived fields in your own workflow
Recommended first production path
For most teams:- sync the fund directory
- register a webhook endpoint and fund-monitoring subscription
- read event feeds periodically to catch missed deliveries and load earlier records