July 2026

June 17, 2026

Base Company data: adding new fields

We are adding new fields to expand company headquarters information.

Data field	Description	Data type
headquarters_location.city	City of the company headquarters	String
headquarters_location.street	Street address of the company headquarters	String
headquarters_location.apartment	Apartment number of the company headquarters	String
headquarters_location.suite	Suite of the company headquarters	String
headquarters_location.zip_code	ZIP / postal code of the company headquarters	String

July 1, 2026

Clean Company data: data fields changes

Clean Company data is migrating to use the updated Base Company data structure as its source. As part of this transition, two fields will no longer contain data and will be removed across upcoming August dump.

Data field	July dump	August dump
company_ticker	No longer populated. The field remains present in the schema but will consistently return null or empty values.	Field removed from the schema. Breaking: Remove all dependencies on this field before the August dump.
company_exchange	No longer populated. The field remains present in the schema but will consistently return null or empty values.	Field removed from the schema. Breaking: Remove all dependencies on this field before the August dump.

July 1, 2026

Multi-source Company data: adding new fields

Adding new fields to improve the granularity of HQ address data and to expose a full structured list of all company locations.

Data field	Description	Data type
hq_latitude	Geographic latitude coordinate of the company's headquarters	Double
hq_longitude	Geographic longitude coordinate of the company's headquarters	Double
hq_apartment	Apartment number or unit identifier for the HQ address, when applicable	String
hq_suite	Suite number or office designator for the HQ address, when applicable	String
company_locations_full[].city	City name of the company location	String
company_locations_full[].state	State of the company location	String
company_locations_full[].street	Street address of the company location	String
company_locations_full[].zip_code	Postal or ZIP code of the company location	String
company_locations_full[].latitude	Geographic latitude coordinate of the company location	Double
company_locations_full[].longitude	Geographic longitude coordinate of the company location	Double

July 1, 2026

Multi-source Employee data: adding new fields

Adding new fields

Adding new fields to surface academic background, career trajectory, and activity signals.

Data field	Description	Data type
institution_ranking_score	Highest QS university ranking score across the employee's education institutions, matched by normalized institution name. null if no institution matches	Double
months_in_management	Total months spent in management-level roles. Calculated as the union of these positions, so overlapping roles aren't counted twice	Long
post_frequency_yearly	Count of professional network posts over the past 12 months	Double
posting_recency	Date of the employee's most recent post	Date
engagement_per_post	Average engagement (reactions and comments) per post	Double
influence_score	Composite 0–100 social-influence score: a weighted, log-scaled blend of post frequency (0.2), engagement per post (0.5), and follower count (0.3), each capped at a fixed, precomputed 99th-percentile threshold. Defaults to 0.0	Double
activity[].created_at	Creation timestamp of the activity item	Timestamp
activity[].updated_at	Last-updated timestamp of the activity item	Timestamp

Adding a tenure_stats struct

A new nested struct capturing per-company tenure statistics in months, derived from the employee's company-linked experience.

Data field	Description	Data type
tenure_stats	Per-company tenure statistics in months, with concurrent roles at the same company counted once. It presents raw data without plausibility checks, so some values might be unrealistic. null if the employee has no datable, company-linked experience	Struct
tenure_stats.avg_tenure_months	Average total tenure per company	Double
tenure_stats.median_tenure	Median total tenure per company	Double
tenure_stats.current_tenure	Tenure at the current (active) position. null if not currently employed	Double
tenure_stats.longest_tenure	Longest total tenure at a single company	Double

Adding a internal_promotion_rate struct

A new nested struct quantifying internal career progression. Promotions are inferred from position-title changes within the same company, ordered by start date.

Data field	Description	Data type
internal_promotion_rate	Internal promotion metrics, derived from position-title changes within the same company, ordered by start date, counting only changes where the new role starts strictly after the previous role	Struct
internal_promotion_rate.promotion_count	Count of internal title changes (promotions). 0 if none	Integer
internal_promotion_rate.avg_months_per_promotion	Average months between consecutive promotions. null with fewer than two promotions	Double
internal_promotion_rate.recently_promoted	True if a promotion occurred within the last 3 months	Boolean

July 10, 2026

Company Posts API: adding new endpoints

We now offer access to Company Posts data through an API. Use the following endpoints to explore the data:

Method	Endpoint
POST	/v2/company_post/search/filter
POST	/v2/company_post/search/es_dsl
GET	/v2/company_post/collect/{post_id}

Find more information in Company Posts API.

July 27, 2026

Response headers changes

We are planning several updates to API response headers that could impact your workflows. See below for information on the affected response headers.

Action	Response header	Notes
Removing	x-subscription-active	"x-subscription-active" response header will no longer be returned in API Search responses.
Changing	x-credits-remaining	"x-credits-remaining" value will update to display all available data collection credits.

July 27, 2026

Scheduled maintenance

Scheduled maintenance is planned for July 27th, from 8 to 10 AM EET. During this time, all API endpoints and the self-service dashboard will be temporarily unavailable. Any requests sent will receive a 503 Service Unavailable error. Please plan your integrations accordingly.