VendorCensus
Menu

Technographic data API

Try the public VendorCensus research API for company technographics, observed vendor customers, and reviewed disclosure events. Responses include coverage dates and source limits.

Initial coverage sample · reviewed (UTC)

Real public-source records, manually reviewed. This is a dated snapshot, not a continuous live feed or a representative market survey.

Try a real endpoint

The request runs against this site’s reviewed sample. Public endpoints require no API key.

GET /api/public/companies?domain=linear.app

Choose an endpoint and send a request to see its response.

A public research sandbox

These read-only endpoints query the same reviewed records displayed on this site. No sandbox key is required for public company and vendor records. Event-company details require a signed-in VendorCensus session. The dataset is small and is not a comprehensive commercial enrichment feed.

Endpoints and response behavior

Use /api/public/companies?domain=linear.app for exact-domain matching and /api/public/vendors?vendor=aws for observed company relationships. Use /api/public/events for anonymized reviewed changes. Invalid company domains return 400; well-formed domains outside coverage return an empty result with an explicit not-observed status.

The public endpoints are GET-only. There is no arbitrary URL fetching, contact enrichment, write operation, or bulk export endpoint. Coverage and review dates are part of the response.

Job-board data and alternative data

The analyst page reads a fixed inventory of public job-board endpoints. The API exposes a narrow title-matched job feed at /api/public/jobs. A failed board check is reported separately and never treated as proof that a role closed.

For alternative-data research, preserve the observation date and source version independently. A newly collected record is not automatically a new customer or adoption event.

Explore related research

What the evidence can tell you

A public job board supports an ATS observation. A subprocessor disclosure identifies a provider that may process data for particular services. A vendor customer story describes a published relationship. These sources have different scopes and are labeled separately.

Counts cover the records on these pages, not the whole market. No observation in our covered sources does not mean a company does not use a vendor. Source recency and unresolved conflicts affect confidence; observations do not establish spend, renewal timing, or customer churn.

Read our methodology · Understand coverage

Start with the evidence.

Create a free VendorCensus account. The public research above is available without signing in.

Create a free account