Company & Product Catalog
No breaking changes. v3 company objects gain provenance detail on description (AI-generated vs human-reviewed) and expanded per-round funding detail. All existing fields keep their names, types, and semantics.
Status: Additive only
Social profile fields are renamed, and optional#
v3 names these socialProfile and socialProfileId; v2 called them linkedinUrl and linkedinId. A company record does not require a social profile, so both are nullable wherever they appear — Company Enrich, Company Match, company relationships, and the company nested inside a person’s workExperience.
companyId, website, socialProfile, or socialProfileId, and Company Match resolves on any one of companyName, website, socialProfile, or socialProfileId. Store aggkCompanyId as the stable identifier.Company Match takes the same filters as v2#
Every attribute filter v2 Company Match accepts — companyType, industry, country, region, locality, employeeCountRange, revenueRangeInferred, primaryExchange, primaryTicker, latestFundingStage, the four funding ranges, and keywords — is on v3 under the same name, with the same and/or/not semantics. Filters port across as they stand.
The one difference is how you name the company. v2 types name, website, socialProfile, and socialProfileId as or/not filters; v3 takes them as plain strings — name is companyName, and all four are hard requirements. A v2 body sending one value per field maps directly; one sending several candidate names, or excluding a name with not, belongs in Discover.
Catalog IDs are stable#
Product and category IDs are version-independent — IDs you’ve stored from v2 remain valid on v3, and vendorgraphic queries accept them unchanged.
What to do#
Nothing is required. Adopt the new fields opportunistically when you move paths to /v3/.