Sending data into HRConnext (writing)

Pick scopes marked "write" when making a key: add departments (org:write) · add employees and change work data such as name, e-mail, position, branch, hire date (employees:write) · file leave for employees (leave:write) — it goes to their approver in LINE as usual and balances change only once approved (approving through the API isn't possible — the approver decides in LINE) · send punches from time clocks and ask for punch fixes for employees (attendance:write) — punches follow the same rules as checking in on LINE (late / early and the company's deduction for unworked time, if switched on), show a "Time clock" label on the attendance page, and re-sending never doubles them; fixes go to the approver · submit expense claims for employees with jpg / png / pdf receipts (expense:write) — to the approver as usual; photos lose their hidden data (such as where they were taken) before they're stored · a key that writes acts for the person who made it and can only do what they may do in the app; if that person is closed or loses the permission, the key stops writing at once (reading still works) · employee status (leaving), salary, national ID, bank account and religion can't be changed through the API — do it in the app · every write is in the activity log as "DevConnext API · key name (for the maker)" · the company's package must include writing (otherwise write_not_in_plan) · connected systems should send an Idempotency-Key every time (safe retries), If-Match when changing, and try ?dry_run=true first to see what would change without saving.