Changelog

October 7, 2026

• New recordClass and subjectType fields — Every record returned by /api/v1/search and /api/v1/entity/{id} now carries two more fields: recordClass, which says what kind of government record it is, and subjectType, which says whether the record is about an organization or a person. Both are always a non-empty string on every code path, so you can branch on them without a presence check. See Record Classes for the seven values and what each one means.
• Nothing else changed — No field was removed or renamed, existing field values and result ordering are unchanged, and meta.total is unaffected, so a client that ignores the two new keys sees exactly what it saw before. If you validate responses against a strict schema, or map them onto a fixed set of columns, these are two new keys to allow. /api/v1/batch does not include them.
• /api/v1/search takes a new record_class parameter — The recordClass field above tells you what kind of record each result is; this parameter lets you ask for only the kinds you want. Pass record_class=all for the behaviour before this change, or name the classes you want, for example record_class=registry_entity,license. An unrecognised value returns 400 listing the valid set. Full parameter reference on Search Entities.
• /api/v1/search's default result set is now two classes — registry_entity (state business-entity registrations) and federal_registration (authoritative federal registers of organisations). Records of other classes have not gone anywhere and are returned whenever you ask for them explicitly. The classes applied to a response are echoed back in meta.record_class.
• If you page through results, meta.total is not narrowed by record_class — total is estimated separately from the result rows, so a filtered request can report more records than the filter returns. Coverage of state business-entity registrations also varies considerably between jurisdictions, so in some places a default search returns noticeably fewer rows than record_class=all does. Both are properties of the underlying data, not a failed query.

October 5, 2026

• lastUpdated is now nullable — GET /api/v1/states returns lastUpdated: null for states where we hold no verified scrape timestamp, instead of a placeholder date. See Data Freshness. entityCount is unchanged.
• State page totals now use the measured record count — The "entities available" figure on /states/{code} reports our measured per-state count rather than the sum of the per-type index, which was incomplete for several states. Per-type breakdowns are labelled as a partial sample where the index does not cover the full set.

March 18, 2026

• Federal data enrichment — New ?include=federal parameter on entity lookups. Cross-reference any business with SEC filings, lobbying disclosures, and government contracts.
• Lobbying endpoint — New /api/v1/lobbying/search endpoint for searching Senate LDA disclosures.
• Contracts endpoint — New /api/v1/contracts/search endpoint for searching federal government contracts from USASpending.gov.

March 1, 2026

• SEC EDGAR search — New /api/v1/sec/search endpoint with support for company name, CIK, SIC code, and form type filtering.
• Batch endpoint improvements — Added federal enrichment support to batch queries.

February 15, 2026

• Batch lookup — New /api/v1/batch endpoint for running up to 25 queries in a single request.
• Cross-state search — Batch queries can now omit the state parameter for cross-state searches (5 credits).

February 1, 2026

• 50-state coverage — All US states now available via the API.
• Registered agent search — New agent parameter on the search endpoint.
• Status and type filtering — Filter results by entity status and type.

January 15, 2026

• Initial launch — Filed API goes live with search and entity detail endpoints.
• Free tier — 100 lookups/month, no credit card required.