Explore the API documentation
Review the available API documentation when planning your integration.
API documentationStart with the business handoff
Identify the action that needs to cross between systems: a quotation request, an issuance step, payment information or a service update. Define who owns each system and the information that must be exchanged before discussing implementation.
Review interfaces and exception handling
An API connection needs more than a successful example. Discuss authentication, available fields, failure responses, duplicate requests and responsibility for unresolved work. Confirm these requirements with the owners of the connected systems.
Connect digital channels to the operation
Portals and mobile access can extend service beyond the back office. Agree which users need access, which records they should see and which actions are included. Product availability and implementation scope should be confirmed during the walkthrough.
Prepare for a technical discovery session
Bring interface documentation you are authorised to share, sample field definitions and an anonymised end-to-end journey. The Insurance Cloud team can discuss the required insurer or payment connection. Do not include credentials or live customer data in a public demo enquiry.
Questions, answered
Are all insurer and payment integrations available by default?
No. Integration scope depends on the systems, interfaces and workflow requirements involved. Confirm the specific connection before agreeing an implementation.
Can we discuss portals and mobile access?
Yes. These are included in the platform discussion. Ask the team to confirm the current product, user roles and actions available for your intended use case.