Integrations
What is an API?
-
An API (Application Programming Interface) integration lets two software systems communicate automatically. It moves data between systems and triggers actions without manual input.
-
For IRIS customers, this commonly means connecting accountancy, payroll or HR systems to other business tools (e.g. ATS, CRM, LMS etc).
Why use API integrations?
-
Save time by reducing manual data entry.
-
Improve accuracy by avoiding transcription errors.
-
Keep systems in sync so records and reports are up to date.
-
Enable automation of routine tasks
Common use cases
-
Provisioning new employees
-
Importing employee data to other down stream systems
-
Real Time Reporting
How an API integration typically works
-
Authenticate: you grant permission (OAuth token) for systems to talk to each other.
-
Map data: choose which fields in one system match fields in the other.
-
Transfer or trigger: data is pushed or pulled on a schedule, on demand, or via webhooks (real‑time events).
-
Monitor: review logs and status to confirm successful transfers.
Security and data privacy
-
Integrations should use secure authentication and encrypted connections (HTTPS).
-
Only give the minimum required permissions and rotate keys where possible.
-
Check that data handling complies with your organisation’s policies and relevant regulations.
Getting started
-
If you want a pre-built, supported connector, rfer to: Partner integrations.
-
If you’re developing a custom connection or using third‑party tools, see: Non‑partner integrations.
-
Typical prerequisites:
-
An IRIS account with appropriate access rights
-
-
API credentials (key or OAuth access)
-
A test/sandbox environment for development
-
A data mapping plan and error‑handling strategy
Best practice tips
-
Start in a sandbox and test thoroughly before going live.
-
Log and monitor integration activity and errors.
-
Implement retry logic for transient failures and alerting for persistent issues.
-
Keep documentation of your configuration and data mappings.