POST Requests
Subscribe to employee profile changes by:
- Submitting a list of employee IDs
- Querying employee profiles using search filters
- Querying employee profiles using the ES DSL schema.
Use Elasticsearch schema to specify the changes you want to be notified about.
Use search filters to specify the changes you want to be notified about.
Subscriptions using IDs
Submit profile IDs to be notified of changes in that specific range.
Response codes
See the list of possible error codes.
Use endpoint /v1/subscriptions/professional_network/employee/es_dsl to specify a range of profiles from which you want to see the updates.
The following filters are not available in webhook ES DSL requests:
- created
- last_updated
- date_from from member_education and member_experience collections
- and date_to from member_education and member_experience collections
- Prepare your request using the following request by adding select filters and your webhook URL to the template:
- Insert your Employee API token instead of {JWT}.
- Insert your Elasticsearch query in the"es_dsl_query": {} section.
- Import the cURL to any API-compatible application.
- Send the request.
- You will start getting updates on select profiles after two days.
You will see a subscription ID as an output for your POST request. However, you can ignore this ID since the necessary data will be provided in the webhook updates. You can retrieve employee data using the IDs visible in the webhook text.
Response codes
See the list of possible error codes.
Use endpoint /v1/subscriptions/professional_network/employee/filter to specify a range of profiles you want to see the updates from:
The following filters are not available in webhook search filter requests:
Note that the following filters are not available in search filter requests:
- created_at_gte and created_at_lte
- last_updated_gte and last_updated_at_lte
- experience_date_from and experience_date_to
- education_date_from and education_date_to
- Prepare your request using the following request by adding select filters and your webhook URL to the template:
- Insert your Employee API token instead of {JWT}.
- Add the selected filters in the "filters": {} section.
- Import the prepared cURL request to any API-compatible application.
- Send the request.
- You will start getting updates on select profiles after two days.
You will see a subscription ID as an output for your POST request. However, you can ignore this ID since the necessary data will be provided in the webhook updates. You can retrieve employee data using the employee IDs visible in the webhook text.
Response codes
See the list of possible error codes.
Use the endpoint /v1/subscriptions/professional_network/employee/id_file to submit a list of IDs in a CSV or Txt file to subscribe to changes in a range of profiles. Check the example for the ID list formatting:
- Prepare the IDs file in a CSV or Txt format. Make sure the list only contains numeric IDs.
Avoid any additional headings in the file. The request will fail if non-numeric data is present in the file.
- Paste in your JWT token instead of {JWT} and your webhook URL in the cURL request template:
- Import the edited cURL request to Postman or any other API-compatible application.
Further instructions are for the POST requests using Postman.
- Click Body:

- Upload the IDs file by clicking the Select Files button in the Value column:

- Send the request.
- You will start getting updates on select profiles after two days.
You will see a subscription ID as an output for your POST request. However, you can ignore this ID since the necessary data will be provided in the webhook updates. You can retrieve employee data using the employee IDs visible in the webhook text.
Keep in mind that to view specific changes to an employee profile, you will need to access the profile data using either the Employee API collection endpoints or the Bulk Collect Employee endpoints.
You have received a webhook notification about an update in one employee profile:
To see the exact changes in the profile, you will have to use the profile ID in the following endpoint:
Function | Endpoint |
---|---|
GET | /v1/professional_network/employee/collect/{employee_id} |
Collection endpoints
You have received a webhook notification about updates in several employee profiles:
To identify the changes in these profiles, you need to export the IDs in a CSV or TXT file and use them with the following Bulk Collect endpoints:
Function | Endpoint |
---|---|
POST | /v1/professional_network/employee/bulk_collect/id_file |
GET | /v1/bulk_collect/{data_request_id}/files |
GET | /v1/bulk_collect/{data_request_id}/files/{file_name} |
Follow the instructions here to successfully collect the employee data (from left to right):
GET the file name
GET the file