Subscribe to Changes

overview set up webhooks to track employee job position changes select the employees of interest by submitting a list of employee ids selecting profiles using elasticsearch schema (es dsl) you can also choose to be notified of changes to any employee in our database choose the subscription method that fits you best subscribe to changes /#elasticsearch post requests select employees you want to track by using clean employees es dsl schema subscribe to changes /#id list post requests select employees you want to track using their profile ids subscribe to changes /#subscribe to all changes subscribe to experience changes from all available employees elasticsearch post requests use endpoint /v2/subscriptions/experience changes/es dsl to specify a range of profiles from which you want to see the updates keep in mind that last updated filter is not available for subscription requests elasticsearch dsl docid\ pkoqnjhsbflf7svuhv5au endpoint usage prepare your request using the template below 1\ insert your api key instead of {api key} 2\ paste your webhook url instead of {your webhook url} 3 paste in prepared es dsl query request body template curl x 'post' \\ 'https //api coresignal com/cdapi/v2/subscriptions/experience changes/es dsl' \\ h 'accept application/json' \\ h 'apikey {api key}' \\ h 'content type application/json' \\ d '{ "webhook url" "{your webhook url}", "es dsl query" {} }' request example example request curl x 'post' \\ 'https //api coresignal com/cdapi/v2/subscriptions/experience changes/es dsl' \\ h 'accept application/json' \\ h 'apikey {api key}' \\ h 'content type application/json' \\ d '{ "webhook url" "{your webhook url}", "es dsl query" { "query" { "match" { "full name" { "query" "john smith", "operator" "and" } } } } }' 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 webhook updates will provide the necessary data you can retrieve employee data using the employee ids (member ids) visible in the webhook text id list post requests use the endpoint /v2/subscriptions/experience changes/ids to order a position change subscription of specific employees using a profile id list endpoint usage prepare your request using the template below 1\ insert your api key instead of {api key} 2\ paste your webhook url instead of {your webhook url} 3 insert collected employee (member) ids instead of {integer ids} curl request curl x 'post' \\ 'https //api coresignal com/cdapi/v2/subscriptions/experience changes/ids' \\ h 'accept application/json' \\ h 'apikey {api key}' \\ h 'content type application/json' \\ d '{ "webhook url" "{your webhook url}", "ids" \[ {integer ids} ] }' import the edited curl request to postman or any other 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 webhook updates will provide the necessary data you can retrieve employee data using the employee ids (member ids) visible in the webhook text subscribe to all changes use the endpoint /v2/subscriptions/experience changes/all to order subscriptions and get notified of changes from all employees available in our database if you choose to track all available employees' job position changes, expect to receive 500,000 or more update messages in a week endpoint usage prepare your request using the template below 1\ insert your api key instead of {api key} 2\ paste your webhook url instead of {your webhook url} curl x 'post' \\ 'https //api coresignal com/cdapi//v2/subscriptions/experience changes/all' \\ h 'accept application/json' \\ h 'apikey {api key}' \\ h 'content type application/json' \\ d '{ "webhook url" "{your webhook url}" }' import the edited curl request to postman or any other 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 webhook updates will provide the necessary data you can retrieve employee data using the employee ids (member ids) visible in the webhook text following steps remember that to view specific changes in an employee's profile, you will need to access the profile data using the clean employee api collection endpoints (collect or bulk collect) single profile update you have received a webhook notification about an update in one profile webhook { "member id" 13984834, "change type" "changed" } to see the exact changes in the profile, you will have to use the profile id in the following endpoint request type endpoint get /v2/employee clean/collect/{employee id} multiple profile updates you have received a webhook notification about updates in several profiles webhook { "member id" 123, "change type" "changed" }, { "member id" 124, "change type" "changed" }, { "member id" 125, "change type" "changed" } to identify the changes in these profiles, you need to export the employee ids in a csv or txt file and use them with the following bulk collect endpoints request type endpoint post /v2/data requests/employee clean/id file get /v2/data requests/{data request id}/files get /v2/data requests/{data request id}/files/{file name} follow the instructions here to successfully collect the employee data (from left to right) post requests docid\ w4l57jlca9itm7gluol3t get requests docid\ cudq9fvnuysab0mdjgscb get requests docid\ cudq9fvnuysab0mdjgscb