Skip to main content
Use this guide to assemble a repeatable renewal or counterparty review packet for a public company. Preserve the filings and event records that support the packet; your team retains responsibility for underwriting criteria, scoring, and coverage decisions.

​
Build the review packet

Use each route for its documented record type. An event result is a research input, not a determination of fraud, claim likelihood, or coverage.

​
Check one renewal candidate

For a filed controls disclosure, retrieve the source section separately:

​
Keep the review boundary clear

Capture accession numbers, filing URLs, section keys, dates, and requestId with the packet. Treat missing, partial, or unavailable results as review conditions, not as evidence that a condition does not exist. The API does not replace primary-source review, legal analysis, underwriting judgment, or your organization’s retention policy.

​
Next action

Run the four reads for one renewal candidate, then compare the resulting evidence record with the packet your team uses today. Add a route only when its fields and source identity satisfy that packet’s acceptance criteria.

Filing search

Find filings and retain their source identity.

Event APIs

Inspect event-specific filters and response fields.

Request diagnostics

Keep an investigation record for partial or failed reads.