Conventions

How field names, timestamps, IDs, countries, industries, and search filters work across the API.

The conventions below apply to every endpoint unless a section says otherwise.

Field names

snake_case everywhere in requests and responses.

Timestamps

ISO 8601 in UTC, for example 2026-05-11T07:52:14.446Z. A few endpoints return Unix seconds; those are called out per field.

IDs

Opaque strings. Do not attempt to parse them. Some IDs are LinkedIn URLs (for example https://www.linkedin.com/company/stripe); treat them as opaque too.

Countries

ISO 3166-1 alpha-2 codes (US, SG, GB, ID). The sentinel WORLD means "any country".

Industries

The API accepts common lowercase aliases (for example saas, fintech, banking) and normalizes them to canonical provider values internally. See the alias table on Discover Companies.

Search logic

When a filter accepts multiple fields and values:

  • Different fields are joined with AND (industry AND location).
  • Multiple values inside the same field are joined with OR (industry.include: ["saas", "fintech"] means saas OR fintech).
  • *.exclude filters are applied as NOT.
  • The WORLD location value means no restriction.

JSON bodies

JSON bodies are required on every POST. Always send Content-Type: application/json.