System integration is a fundamental requirement for modern business operations. This brief technical overview clarifies Linx’s integration capabilities and provides a reference for developers and architects considering their integration options.
Integration Capabilities Overview
The platform provides several methods for connecting external systems, focusing on standard protocols and widely-used technologies.
Core Integration Methods
1. API Integration
The REST plugin serves as the primary method for API connectivity:
- Compatible with REST and SOAP web services.
- Handles standard authentication methods.
- Supports custom header configurations.
- Capable of accepting JSON and XML payloads, which can be further managed and altered in your process.
Read more on the REST plugin documentation
2. Database Connectivity
Database integration options include:
- Native drivers for Oracle and Microsoft SQL Server.
- PostgreSQL native support (upcoming release).
- ODBC driver support for all other database systems.
- Connect and interact with MySQL, SQLite or any other database technology.
- Standard query and data manipulation functionality.
Read more on the Database plugin documentation
3. Additional Integration Protocols
For specific use cases:
- SignalR for real-time communication requirements.
- RabbitMQ for message queue integration.
- GraphQL for complex data querying needs.
Financial System Integration Examples
Xero Integration
- OAuth 2.0 connection management—This new feature allows for streamlined interaction with Xero’s authentication service, which manages authentication and connection. It allows you to connect to any Xero API using only a user and tenant ID.
- Automated token refresh handling.
- Standard API access.
Read more on the Xero plugin documentation
QuickBooks Integration
- Basic API connectivity.
- Single-tenant configuration (at the time of writing).
Read more on the Quickbooks plugin documentation
Technical Considerations
When implementing integrations with Linx, consider the following aspects:
API-First Approach
-
- Standard REST implementations work well with most modern systems.
- Custom headers and authentication can be configured as needed.
- SOAP support is available for legacy systems.
Database Integration
-
- Direct database access where APIs aren’t available.
- Support for any SQL operations supported by the driver.
- Connection pooling and transaction management are possible.
Message Queue Integration
-
- Useful for asynchronous processing.
- Supports standard message queue protocols.
- Helpful for distributed system architectures.
Implementation Notes
Linx follows industry-standard protocols and methods for integration. This means:
- Most modern systems can integrate using REST APIs.
- Legacy systems can be accessed via databases or web services – and made available by creating APIs to facilitate interaction.
- Real-time requirements can be handled through SignalR.
- Complex data scenarios can utilise GraphQL.
Case-by-Case Evaluation
Each integration scenario may have unique requirements. Technical teams are encouraged to evaluate specific needs based on:
- The target system’s available integration points.
- Data volume and frequency requirements.
- Security and authentication requirements.
- Performance considerations.
We are happy to assist in this evaluation to see where Linx can assist and streamline your development strategy.