Mapping Endpoint

data type base employee api query type coresignal's custom endpoint url https //api coresignal com/cdapi/v2/employee base/map/ids since ids used in the base employee api might be different from those used in employee api, you need to map them the mapping endpoint is developed for quick and accurate migration between apis request body you need to enter the list of ids for it to be mapped the mapping ids list can include up to 10k ids example input code \[ 11111111, 22222222, 333333333 ] response body response structure should look like this data point description data type total id count a total number of input ids integer mapped id count a number of successfully mapped ids from the given list integer unmapped id count a number of unsuccessfully mapped ids from the given list integer mapped ids an object containing key value pairs here, the keys are string representations of ids in employee structure, and the values are their numeric equivalents in the new base employee structure object unmapped ids an array containing any unmapped ids array response body example { "total id count" 3, "mapped id count" 3, "unmapped id count" 0, "mapped ids" { "11111111" 11111111, "22222222" 22222222, "333333333" 333333333 }, "unmapped ids" \[] }