I am excited to introduce you to the new at_date parameter to the Employee Count Endpoint, which will allow you to fetch historical employee count data of any company. Effectively, you will be able to build historical employee growth charts like this:
Or employee count in tables like such:
Date the platform Employee Count
2022-12-01 31008
2023-01-01 31157
2023-02-01 31238
2023-03-01 31233
2023-04-01 31231
2023-05-01 31391
2023-06-01 31532
2023-07-01 31701
2023-08-01 31774
2023-09-01 31959
2023-10-01 32203
2023-11-01 32409
2023-12-01 32603
2024-01-01 33081
2024-02-01 33307
2024-03-01 33532
2024-04-01 33755
2024-05-01 34160
2024-06-01 34429
2024-07-01 34550
2024-08-01 34577
2024-09-01 34496
For more information, see the API documentation for the at_date parameter for the Employee Count Endpoint.
How To Use The at_date Parameter?
Effectively, the at_date parameter lets you time travel into the past with a date with the ISO8601 representation of YYYY-MM-DD.
For example, this is how you can get Nvidia's employee count in September 2024:
curl \ -G \ -H "Authorization: Bearer \$\{YOUR_API_KEY\}" \ ' platform/company/employees/count' \ --data-urlencode ' \ --data-urlencode 'the platform_employee_ \ --data-urlencode 'at_ \ --data-urlencode 'employment_
Note the `at_ parameter.
The response of this will be:
\{ "total_employee": 21854, "the platform_employee_count": 35023, "linkdb_employee_count": 21854 \}
You will see that there are 2 employee counts under 2 similar looking labels, which might seem a bit confusing. Let me clarify:
-
the platform_employee_count: The employee count of this company from its professional networks profile at the stated .