Discussions

You posted an email saying:

Tags werden in Zukunft nicht mehr an eine einzelne Bewerbung gekoppelt sein, sondern an eine:n Kandidat:in. Der Endpoint Update Application Tags wird Tags auf der Ebene des Bewerbers hinzufügen. Das bedeutet folglich, dass sich in den Endpoints Get Applications und Get All Applications die Query Params containsTag und notContainsTag auf die/den Kandidat:in beziehen und nicht auf die einzelne Bewerbung. Schematisch werden sich die Endpoints nicht verändern.

Translation to English

tags will no longer be linked to an individual application, but to a candidate. The Update Application Tags endpoint will add tags at the applicant level. This means that in the Get Applications and Get All Applications endpoints, the query params containsTag and notContainsTag refer to the candidate and not to the individual application. Schematically, the endpoints will not change.

I have a connection between JOIN and HRWorks. Once a day new applicants for a given job are transferred to HRWorks. If that is successful, the JOIN application for that individual gets tagged with the id of the application of that individual in HRWorks. This way I can make sure that I have no double entries.

The announced change will not really work for me and I wonder what the reasons are for the change. After all, the endpoint is update Application tag and not update applicant tag. Applicants may try to apply for multiple jobs and I currently don't see another "cheap" (in terms of payloads) way to have a meaningful mapping as there are no other fields available through the API (reading through all the notes is not an option:D)

Anyone an idea?