- track filings for a watchlist of companies
- surface dividend and board-change signals
- route issuer events into internal review workflows
- load company history and receive new events for tracked issuers
What Rangler gives you
The issuer workflow package is built from:GET /v1/companiesGET /v1/companies/{company_id}GET /v1/companies/{company_id}/filingsGET /v1/companies/{company_id}/eventsGET /v1/events?type=filing.new&type=board_change.detected&type=dividend.declared- webhook subscriptions filtered by issuer event type and company scope
Start with webhooks
Start with webhooks when issuer updates should drive a customer-facing product, alert, or internal review workflow.Company watchlist sync
Fetch the current company directory:Filings for one issuer
Check issuer events for missed deliveries
ranglerpy:
Recommended rule
In the portal:- Create a webhook endpoint
- Choose the Issuer monitoring preset
- Keep event types:
filing.newboard_change.detecteddividend.declared
- Add company IDs for your tracked issuer set
- Leave fund IDs empty
Partner payload pattern
Receiver flow:- receive a matched issuer event
- verify the webhook signature
- use
company_id,source_kind,source_id, andsource_urlto record where the event came from - fetch richer company or filing detail through the API if needed
- fan the event out to your own alerting or internal review systems
Example issuer webhook payload
Source-backed event detail
Rangler activity and delivery views show source fields including:source_kindsource_idsource_urlsource_published_at
Recommended first production path
For most teams:- sync company IDs through API reads
- register a webhook endpoint and issuer-monitoring subscription
- read event feeds periodically to catch missed deliveries and load earlier records