![Variation=Brandmark, Color=WhiteVector.svg]](https://support.q7leader.com/hubfs/Variation=Brandmark%2c%20Color=WhiteVector.svg){kind=small}
Administrator - Guide on Integration API
This guide covers common integration use cases, key data fields, and how to get started.
What is Q7Leader?
Q7Leader is a talent management platform with features like:
- Role Descriptions (RDPs): defining job expectations and competencies
- Objectives: goal setting and tracking
- TeamScan: talent reviews and succession planning
- Conversations: structured feedback between managers and team members
Why Integrate?
The most common use case is syncing employee data from your HRIS (or social secretariat system) to Q7Leader - eliminating double data entry and keeping your organizational structure, permissions, and access control consistent.
Keeping this data accurate manually becomes unsustainable, and errors directly impact the business.
Other use cases include:
- Data extraction - pulling talent data from Q7Leader into reporting or BI tools
- Bulk imports - loading objectives or other data in bulk
- LMS integration - connecting to learning management systems to drive appropriate content
Typical Fields
Member (Employee) /member
| HRIS Field | Q7Leader Field | Notes |
|---|---|---|
| Employee ID | custom_fields |
External identifier for mapping |
| First Name | first_name |
|
| Last Name | last_name |
|
| Department | department_id |
|
| Manager | manager_id |
Q7Leader member ID of manager |
| Hire Date | time_in_company |
Format: YYYY-MM-DD |
| End Date | end_time_in_company |
Needed for TeamScan |
| Role Description Profile | rdp_id |
Job description / role definition |
| Country | country |
Optional |
| Gender | gender |
Used for pay transparency reporting |
| Date of Birth | birthday |
Format: YYYY-MM-DD |
| Time in Role | m_time_in_role |
Optional. Format: YYYY-MM-DD |
| Custom attributes | custom_fields |
For additional attributes |
Department /department
| HRIS Field | Q7Leader Field | Notes |
|---|---|---|
| Department Name | name |
|
| Parent Department | parent_department_id |
Required. For nested hierarchy |
| Department Head | head_id |
Affects department permissions |
Roles & Permissions /user /member/{member}/access_rights
| Concept | Q7Leader Field | Notes |
|---|---|---|
| User role (Employee, Manager, HRBP, etc.) | role_id |
Via /user endpoint |
| Departmental access | department_id, read, write |
See Department below |
Note: Role assignment via API can be restricted per role. This is configured in Q7Leader under Settings → Roles.
Getting Started
| Resource | Location |
|---|---|
| API Reference | my.q7leader.com/docs/api |
| Feature Documentation | support.q7leader.com |
| API Token | Generated in Q7Leader: Settings → API |
| Test Environment | Available on request |