Before using apis please have a look at: Getting started
Employee or Individual in the Legacy administration
This set of APIs will provide endpoints to retrieve or to define some information on the employee or individual of the company when you are using the Legacy Core Hr. ```If you are using the HUB module do not use the legacy endpoints```. (There are some exceptions to this rule: SpecifNodes related API (with cautious), photos, documents, and basic searches on individual. See the documentation below for exception.)Introduction
Because the platform is allowing users that are not employee (like individual with a freelance contract) and makes available the possibility to store relatives in the database, there is a notion of Individual. An employee is an individual but not all employees are individuals. Thus, the endpoint signature varies according to scope of the population targeted. Notice that individuals don’t have employeenumber so the GET method will not use this parameter to identify an individual.Communication devices and postal adresses
An individual may have several communication devices.A communication device can be an e-mail, a phone, private, professional. An individual may have one or several postal addresses.Job
Every employee is linked to a job, coming from a job library. The job library can be defined in Legacy core or in the HUB. It is a hierarchical library.Photo
The photo of the employee displayed in many places inside the solution. This API can be used even if you are using the HUB module.Organization
As you can define as many organizations as you want (hierarchical, functional, ...) in Talentsoft you will be able to retrieve and set the values of links between employees using related endpoints.Managees
Managees are you direct reports in the default organization (hierarchical) and you can access to some information on them.Specif node
Some of the endpoints are related to a technical object called SpecifNode. Key property nodes are part of the specif nodes.Please look at the documentation on libraries to better understand this data type.
So, an employee can be linked to Key property and you can retrieve through API all its key property, delete, update or add new one.
DON’T USE THIS API FOR SETTING HUB data. The only exception could be if you want to add manually some key property to an employee in addition to HUB datasets. Then in that case, and only in that case, you can use the Put and Post endpoint to the set a value of this specific key property tree. Otherwise the process of mirroring will overwrite your settings, and you will loose your values.
Again, if you are using the HUB. There is the possibility to retrieve some datasets info on your employee as HUB data are mirrored in the Legacy Core HR solution, but it will be only the current value. (By example the current value of the Entity of the main situation).