Can I create new employees through the IRIS HR API?

Yes. POST /employees creates a new employee record, and POST /jobs attaches a job to the employee. PUT /employees/{id} updates an existing record by ID.

How do I read the organisation's hierarchy?

Use GET /hierarchy to list all nodes and GET /hierarchy/{id}/path to retrieve the full path from any node back to the root, which gives you each level of the organisational tree.

What are the rate limits for the IRIS HR API?

IRIS does not publish hard per-minute rate limits in the spec; throughput is governed by tenant size and plan. Bulk syncs should run during off-peak hours and use delta filtering rather than full re-fetches.

How do I list employees through Jentic?

Search Jentic for 'list employees in IRIS HR', load the GET /employees operation, and execute it. Jentic exchanges the OAuth credentials for a bearer token and applies it to the request.

Does IRIS HR expose bank details for payroll feeds?

Yes. The /bankdetails resource exposes list and create operations so that payroll engines can read or update employee bank information without going through the IRIS HR UI.

Can I limit what my agent is allowed to do with the IRIS HR API?

Yes. Because you run Jentic One yourself, your own rules decide which IRIS HR operations and credentials the agent may use. Since IRIS HR carries the employee id in the URL path, such as /employees/{id}, you can pin the agent to reading and updating specific records with GET and PUT while leaving out creation, so POST /employees and POST /jobs are unavailable unless you explicitly add them. The stored OAuth credentials are applied only to the calls you have allowed, so the agent cannot reach operations or bank-detail writes you have not enabled.