Mapping Endpoint

Data type:

Query type:

URL:

Base Employee

Coresignal's custom endpoint

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 10,000 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": []
}