create-employee

# Create Employee Exactly 2 API calls. ## Call 1: Get Department + Division (ONE call) ``` GET /employee?fields=id,department(id),employments(id,division(id))&count=1 ``` From the admin employee response, extract: - `department.id` — needed for the new employee - `employments[0].division.id` — needed for inline employment Both come from this single call. Do NOT make a separate GET for employment/division. ## Call 2: Create Employee WITH Inline Employment ```json POST /employee { "firstName": "<first name>", "lastName": "<last name>", "email": "<email>", "dateOfBirth": "<YYYY-MM-DD>", "userType": "NO_ACCESS", "department": {"id": <department_id>}, "employments": [ { "startDate": "<start date from prompt>", "division": {"id": <division_id>}, "isMainEmployer": true, "taxDeductionCode": "loennFraHovedarbeidsgiver" } ] } ``` **Total: 2 calls, 0 errors.** ## userType Selection - `"NO_ACCESS"` — default for most tasks - `"EXTENDED"` — use when prompt mentions "administrator" / "kontoadministrator" / "admin" ## Gotchas - `department` is required — creation fails without it - `startDate` goes on employment, NOT on the employee object - `dateOfBirth` format is "YYYY-MM-DD" - GET /employee with `fields=id,department(id),employments(id,division(id))` returns BOTH department and division in ONE call — do NOT make a second GET