/v1/personal/employees/:uid
Lists of available employees for specific accounting unit.
Example
/v1/personal/employees/88899460-4d0b-421b8d67-2023
Request
GET
uid - accounting unit identifier
Response
200text/json

{
      employee_number: string, employee number
      employee_name: string, employee name
      employee_surname: string, employee surname
      employee_prefix: string, employee prefix
      employee_birth_number: string, employee birth number
      employment_enter_date: date, employment start date in "yyyy-mm-dd" format
      employment_leave_date: date, employment end date in "yyyy-mm-dd" format
      employment_active: boolean, employment active
      employment_number: string, employment number
      employment_position: string, employment position
      employment_name: string, employment name
      employment_place: string, employment place
      department_name: string, department name
      working_hour_start: string, working hour start
      working_hour_end: string, working hour end
      working_schedule: string, working schedule
      working_daily: string, working daily
      working_weekly: string, working weekly
      working_monthly: string, working monthly
}[]
Error
400 bad request
your request doesn't meet requested input
401 not authorized
your request doesn't meet authorization requirements
404 not found
entity you loking for, is missing
460 request error
requested operations wasn't performed, or xml import failed
500 internal error
we encountered some internal server error
503 not available
requested entity is offline and cannot be reached, try again later
/v1/personal/import/xml/:uid
Synchronous attendance or employee XML import for personal unit (only for Pamica). Response will be send after import was successfull, or an error occoured. If so, response will return error message with detailed description.
Request
POSTtext/xml
uid - accounting unit identifier
Request body is required to be valid CZ xml document.
Response
200text/xml
XML response according to CZ xml schema.
Error
400 bad request
your request doesn't meet requested input
401 not authorized
your request doesn't meet authorization requirements
404 not found
entity you loking for, is missing
460 request error
requested operations wasn't performed, or xml import failed
500 internal error
we encountered some internal server error
503 not available
requested entity is offline and cannot be reached, try again later