Broadly, Iress supports several integration patterns for Xplan. The right pattern depends on who is building the integration, who will use it, the level of access required, and the commercial or support model that applies in each region.
Iress Open Standard
A productised API access pattern for common Xplan integration use cases.
This path was designed for third-party applications that need a repeatable way to connect to Xplan across multiple client sites using RESTful API services documented in Swagger. Access is controlled through API keys, user permissions, and agreed capabilities.
This pattern is best suited where the integration uses standard, supported API endpoints and does not require bespoke development by Iress.
Custom API connection
A deeper or more tailored connection where the use case requires additional review, specific capability access, or commercial and contractual terms beyond standard API access.
This may apply where the integration has higher complexity, broader data requirements, higher traffic volumes, or a more sensitive operational impact.
Custom connections are assessed case by case and may require additional governance, technical review, and region-specific approval.
Integration partner
A closer partnership model where Iress and the third party have a more strategic relationship.
This may involve joint planning, agreed support pathways, coordinated go-to-market activity, roadmap alignment, or broader commercial arrangements. This pattern is generally reserved for integrations with clear customer demand, strategic value, and an agreed operating model between Iress and the partner.
Client-specific (bespoke) connection
A connection built or configured for a specific client need.
This is generally used where a client wants to connect Xplan to its own internal systems, reporting platforms, data warehouse, or other proprietary tools. The connection may be delivered by the client, their technology partner, or with support from Iress, depending on the use case and regional process.
Choosing the right pattern
These patterns are not intended to be rigid labels. They help Iress route requests to the right team, assess the level of access required, and apply the right commercial, technical, and risk controls.
Availability, pricing, onboarding steps, and support models may differ by region. For specific guidance, contact the relevant local Iress team.
