Integrations
Connect leave data to your own systems
The integration API gives read-only access to employee, leave, balance and payroll data. Webhooks tell your systems the moment leave is approved or cancelled.
- API keys limited to the scopes you choose
- Webhooks signed with HMAC-SHA256
- Automatic retries for failed deliveries
Read-only integration API
Your own systems read İzin360 data as JSON. Each key can reach only the scopes you choose.
- Separate scopes for the employee list, leave requests, leave balances and the payroll file
- The payroll file is the same as the in-app payroll export (CSV or XLSX)
- The employee list contains no national ID numbers or salary information
- A requests-per-minute limit based on your plan
Secure key management
API keys are created by the company owner. A key is shown only once, when it is created; an unused or suspect key can be revoked with one click.
- Optional expiry date
- The last time each key was used is visible
- The number of keys depends on your plan
Signed webhooks
When the events you choose happen, İzin360 sends a signed request to your endpoint. Your receiving system verifies the signature and timestamp.
- Events for leave submitted, approved, rejected, withdrawn, cancelled and started, and for completed employee offboarding
- Delivery only over HTTPS and only to public internet addresses
- Failed deliveries are retried at increasing intervals; delivery history is shown in the dashboard
- Send a test event to try the connection first
Data minimisation
Webhook payloads carry only what is needed: record IDs, personnel number, dates, day count and status. Names, email addresses and free-text reasons are never sent.
- Health-related leave types are sent only as “On leave”
- If the same event arrives more than once, the event ID lets you filter out duplicates
Connections without code
Not every integration needs development work. Employee data can be imported from a file, and leave can appear in calendar apps through a subscription.
- Bulk employee import from Excel or CSV; the whole file is validated first and errors are shown row by row
- Personal and team iCal subscriptions
- Public API documentation with endpoints, sample responses and a signature verification example
How it works
- 1
Create a key
In the integrations settings, choose the scopes you need, create an API key and store it somewhere safe.
- 2
Add a webhook
Choose your endpoint and the events you want to follow, then save the signing secret in your receiving system.
- 3
Test and go live
Send a test event, check the result in the delivery history and switch your integration on.
Frequently asked questions
Can we write data to İzin360 through the API?
No. The integration API is read-only; it is for reading employee, leave, balance and payroll data. To add employees in bulk, use the Excel or CSV import.
How do we verify that a webhook request came from İzin360?
Every request carries an HMAC-SHA256 signature computed with your signing secret over the timestamp and request body. Your receiving system recomputes and compares the signature and rejects requests with old timestamps. Sample code is in the public API documentation.
Are events lost if our system is temporarily down?
No. Failed deliveries are retried up to 8 times at increasing intervals. After 15 consecutive failed deliveries, the subscription is switched off automatically; once you fix the endpoint, you switch it back on from the dashboard.
What personal data does the API return?
The employee list includes personnel number, full name, email, department, team and start date; national ID numbers and salary information are not in this list. Webhooks carry no names or email addresses either, and health-related leave types are sent only as “On leave”.
Is there a ready-made integration for a particular payroll or HR product?
İzin360 does not offer product-specific connectors. Instead, it provides a standard REST API, webhooks, a CSV/XLSX payroll file and iCal subscriptions that any system can use.
Try it with your own data
Try it free for 30 days; no card needed. Request a demo if you have questions.