I observed that the records returned from the search endpoint, when I applied a filter by dateLastModified, were four hours behind the current time. It appears that the API is parsing the dateLastModified using a timzone offset.
Other search methods, such as Placement, do not function in this way. (it appears that UTC is being used for the dateLastModified)
However, the conduct ought to be identical in both instances, right? Then why is that?
Best regards,
Marianne Fletcher
Please help!
Moderators: StaffingSupport, pmularski, BullhornSupport