--- title: IntelliHR API Integration on Truto slug: intellihr category: HRIS canonical: "https://truto.one/integrations/detail/intellihr/" --- # IntelliHR API Integration on Truto **Category:** HRIS **Status:** Generally available ## Unified APIs ### Unified HRIS API - **Companies** — Companies represent the companies in HRIS - **Employees** — Represents an employee in HRIS - **Employments** — Employments represent a job position at a company. - **Groups** — Groups represent the groups for an Employee - **Job Roles** — Represent the job roles in a company - **Locations** — Locations represent the locations in HRIS ## How it works 1. **Link your customer's IntelliHR account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach IntelliHR.** The Proxy API is a 1-to-1 mapping of the IntelliHR API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Sync employee and job data into your payroll or compensation platform** — If you build payroll or compensation software, you can pull employee demographics, job roles, salaries, and business entity associations from IntelliHR so your customers don't have to manually re-enter workforce data. This keeps compensation calculations accurate and up to date as promotions and role changes happen in IntelliHR. - **Automate IT provisioning and deprovisioning from HR events** — IAM and IT automation platforms can listen for new hires, role changes, and terminations in IntelliHR to automatically provision or revoke access to tools like Google Workspace, Slack, and GitHub. Truto normalizes the employee, group, and location data so you can build department-aware provisioning rules without learning IntelliHR's API quirks. - **Build a live org chart and employee directory for your SaaS product** — Employee engagement, recognition, or internal communications platforms need an accurate picture of who works where. By reading employees, groups, locations, and employments from IntelliHR, your product can maintain a real-time org structure without asking customers to upload CSVs. - **Power compliance workflows with up-to-date workforce data** — Safety, training, and compliance applications need to know which employees hold which roles at which locations to enforce certification requirements. Pulling structured employee, job role, and location data from IntelliHR lets your app match workers to compliance obligations automatically. - **Enrich analytics dashboards with centralized HR data** — People analytics and business intelligence tools can ingest employee, employment, and group data from IntelliHR to power headcount reporting, attrition models, and departmental benchmarks — giving your customers a unified view without manual data exports. ## What you can build - **Automated employee directory sync** — Import employees, their job roles, departments (groups), and office locations from IntelliHR into your product on a scheduled basis so your customers always have a current workforce roster. - **Department-aware access provisioning rules** — Use business unit (group) and location data from IntelliHR to automatically determine which tools and permissions a new hire should receive based on their department and office. - **Real-time org chart generation** — Combine employee, employment, group, and company data from IntelliHR to render a navigable organizational chart inside your product that updates as roles and reporting lines change. - **Multi-entity payroll mapping** — Read business entities (companies) and employment records from IntelliHR to automatically route employees to the correct legal entity and pay schedule in your payroll platform. - **Headcount and location analytics widget** — Aggregate employee counts by group, location, and job role pulled from IntelliHR to surface workforce distribution insights directly inside your analytics dashboard. - **One-click IntelliHR connection for end users** — Let your customers authorize their IntelliHR account through Truto's managed auth flow — no custom OAuth implementation or API key management on your side. ## FAQs ### What authentication method does IntelliHR use? IntelliHR's REST API uses bearer token (API key) authentication. When your end users connect their IntelliHR account through Truto, the auth flow securely captures and stores this token so you never handle credentials directly. ### Which IntelliHR data models are available through Truto's Unified HRIS API? Truto's Unified HRIS API maps IntelliHR's People to Employees, Jobs to Employments and Job Roles, Business Entities to Companies, Business Units to Groups, and Locations to Locations. This covers the core employee lifecycle and organizational structure data. ### Are IntelliHR-specific endpoints like qualifications or training records available? IntelliHR exposes qualification instances and training records through its native API, but these are not part of Truto's Unified HRIS API schema. Truto can build custom tools for these endpoints on request if your use case requires them. ### Does IntelliHR support webhooks for real-time data sync? Yes, IntelliHR natively supports webhooks for events like person.created, job.updated, and job end dates. Truto can help you consume these events as part of a custom integration workflow built on request. ### How does Truto handle pagination and rate limits for IntelliHR? Truto automatically manages pagination across IntelliHR's REST API endpoints so you receive complete result sets without writing cursor logic. Rate limit handling, including retries and backoff, is managed by Truto's proxy layer. ### Can I write data back to IntelliHR or is this read-only? IntelliHR's API supports both read and write operations, including creating people and job records. Specific write capabilities through Truto depend on the tools built for your use case — contact Truto to discuss write support for your integration scenario.