Integrations and Interoperability

See attached document for details.
General Technical Approach - Our goal with the ASPIRE API is to make the ASPIRE platform easily open to integrations. We
are interoperable with multiple technology stacks, and utilize the most current web and
technology standards, allowing integrations to be built by either you or LTi.
Each integration comes with unique requirements and needs to be evaluated individually. We
generally abstract out the integration into our standard internal component and interface model,
then allow the component to navigate the complexity and unique aspects of the external service.
Table of Contents
Integration Technology
General Technical Approach
Integrating with External Web Services
Standard Integrations
API
Overview
Message Format
Resource Format
Transactional Endpoints
Related Articles
ASPIRE Logical Architecture
See attached document for complete details. LTi Technology Solutions, a Microsoft Gold Partner (representing the highest level of competence and expertise with Microsoft technologies), chose the Microsoft .NET Framework (currently version 4.7.2) as a ...
Insurance Integration Modules Video
See linked videos for complete details. The linked videos review details around the Insurance Integrations available for ASPIRE. Click here for video 1 that covers the need for lease insurance and the standard Insurance functionality. A 5 minute ...
Assurant Insurance Integration
See the attached document for complete details. Overview The Assurant Integration affords ASPIRE users the ability to export contract data to Assurant where the insurance coverage is confirmed or a premium is calculated. Assurant then provides an ...
EFT Bank and Company Setup
See attached document for details. Please see the attached guide for specifications on the EFT Bank setup in ASPIRE (Administration > Cash Management > EFT Bank)
ASPIRE Upgrade Preparation Guidance
Summary This article is intended to provide guidance for ASPIRE v5 customers to test a new release of the system prior to deployment for production use. The processes outlined are not representative of all potential configurations and usage of the ...