Introduction on how to integrate with Quinyx | Summary and Q&A

TL;DR

This content discusses the importance of integrating with Clinics, provides information on where to find integration information, and offers best practices and examples for designing and building integrations.

Key Insights

• 👥 Integrating clinics with HR systems is a common practice, as it allows for the inclusion of employees' data in clinics. This integration ensures accurate scheduling, payroll, and vacation balance management.
• 💡 APIs provided by clinics allow customers to access and pull data for various purposes such as business intelligence and custom reporting. SOAP and REST APIs are available, with REST being the preferred API for new functionality.
• 🔄 A typical integration landscape involves multiple steps, starting from HR systems (where employees are entered) to payroll and clinics. Forecasting functionality in clinics helps managers in creating schedules based on employee and forecast data.
• 💻 Integration credentials and API keys are essential for connecting to clinics' APIs. REST credentials can be generated in the account settings, while SOAP API keys can be found in the account settings under domain level.
• 🔑 External identifiers such as group integration keys and unit integration keys need to be created and configured. Unit API keys can be obtained using the get units API key V2 call and used for data retrieval and integration purposes.
• 📝 When creating integration keys, using smart naming conventions can help avoid the need for mapping tables. Concatenation can be used to include relevant information, such as contract type and employment status.
• 🔐 Testing and building integration should be done using the RC (Release Candidate) environment to ensure accuracy and avoid any potential issues in the production environment. Limiting payload size and time periods can also enhance performance.
• ⚙️ Best practices for integration include spreading out concurrent API calls throughout the day and implementing exponential back off when faced with error 429 (too many requests). Documentation and help resources, such as Help Talks, should be utilized for guidance and information.

Transcript

Read and summarize the transcript of this video on Glasp Reader (beta).

Questions & Answers

Q: How can clinics benefit from integrating HR systems with Clinics?

Integrating HR systems with Clinics allows for the seamless transfer of employee information, such as payroll data and leave applications, ensuring accurate and up-to-date records.

Q: What are some examples of common integrations with Clinics?

Common integrations with Clinics include HR integrations for employee data, balance integrations for tracking vacation and sick leave balances, and business intelligence integrations for monitoring worked hours and absences.

Q: Where can users find information about Clinics' APIs?

Users can find information about Clinics' APIs in the online manual, specifically in the SOAP and REST sections. The manual provides details on available calls, endpoints, and best practices for integration.

Q: How can users generate API keys for integration with Clinics?

API keys for integration with Clinics can be generated in the account settings of the Clinics platform. Users need appropriate access permissions to read, add, or modify API keys.

Q: What is a recommended approach for fetching data for a business intelligence system in Clinics?

It is recommended to use the "get units API key V2" call to retrieve API keys for each unit in order to fetch data unit by unit. This approach eliminates the need for mapping tables and ensures data accuracy, even if API keys change or new units are added.

Q: How can users create a new employee in Clinics using API calls?

Users can create a new employee in Clinics by making API calls for updating employees and updating agreements. These calls require specific parameters, such as batch numbers, names, email addresses, role IDs, and contract details.

Q: What are some best practices for configuring the system for integrations with Clinics?

Best practices for configuring the system for Clinics integrations include setting up appropriate integration keys, using naming conventions for agreement templates, and utilizing API keys for data transmission. It is also recommended to limit payload size, time periods, and concurrent calls to optimize integration performance.

Q: How can users test and build integrations with Clinics?

Users should start by testing and building integrations using the RC (release candidate) environment. It is also important to limit payload size, make multiple smaller API calls instead of one large request, and spread out concurrent calls to avoid error 429 (too many requests). Help talks and documentation provide further guidance on integration testing and development.

Summary & Key Takeaways

• Integrations with Clinics are important for HR integration, balance tracking, business intelligence, and payroll purposes.

• The API documentation and help talks are valuable resources for finding information on Clinics integrations.

• Best practices include using API keys, making API calls for data retrieval, and following guidelines for system configuration.