Skip to content
GridRouterhome

Search

Search providers, capabilities and pages

Registry filings API

registry.filings

Filings and statements lodged with a registry or regulator.
providers document it
7

Providers

7 providers document registry filings in their own API docs. None routes it through GridRouter yet. Scores appear as calls are routed.

What counts as a hit:
At least one filing is returned for the entity.

API

Same input for every provider. Set provider.sort to route by price, reliability or latency, or provider.only to pin providers; X-Grid-Max-Cost caps what one call can spend.

Inputs for registry.filings
InputDescription
registration_number*Registry number or CIK (required)
Request
curl https://api.gridrouter.io/v1/run/registry.filings \
  -H "Authorization: Bearer $GRID_API_KEY" \
  -H "Content-Type: application/json" \
  -H "X-Grid-Max-Cost: 0.05" \
  -d '{"input":{"registration_number":"0000320193"},"provider":{"sort":"price"}}'

Fields

The normalized output every provider maps into. Suppliers come from integrated endpoint mappings (verified) or field names in each provider's API docs (claimed by the provider).

Every capability's fields
Output fields for Registry filings
FieldTypePIIDescriptionSupplied by
filing_idstringNoneFiling or accession idNorth Data
form_typestringNoneForm or filing typeNot mapped yet
filed_atdateNoneFiled onNot mapped yet
periodstringNonePeriod coveredNot mapped yet
urlstring · urlNoneDocument URLKyckr
descriptionstringNoneFiling descriptionNorth Data