[0.10] Daniel Teague: API overview and how they benefit Zurich and our partners

What is an API and why is it important to Zurich? Dan gives us a detailed overview, including this very illustrative analogy.

An API is a messenger, like a waiter in a restaurant. It takes your order, takes it to the kitchen (system), where your order is prepared and then returned by the API. You don’t need to know the process, you just get what you ordered.

In the past, we used direct (or point-to-point) connections. You enter your details into the Zurich website, the backend system calculates the details and offers you a product and price. With APIs, you don’t need to be on Zurich’s system. When you buy travel insurance from a holiday website, you’re buying Zurich insurance, but the holiday website doesn’t need to know the complexities of Zurich’s ‘kitchen’ – it’s the waiter that delivers your order.

APIs create efficiencies, deliver more and better innovation and drive growth. APIs already in use by other Business Units can be embedded into your solutions so you can deliver faster, better products on low budgets. They’re helping us to embed insurance with new partners across the globe and connect all the separate parts of our business.

Let us know if you have any great innovations that you’ve deployed locally that could be re-packaged as APIs.

[12:00] Explanatory video

The video explains how Zurich’s open API platform helps you to build, use, manage and share winning APIs. Powered by MuleSoft and Microsoft, the API platform can help you to save up to 75% of the original cost of APIs.

Find out more at www.suite.zurich.com/API

[23.30] Sam Jones with a demo of the Zurich Exchange

Sam walks us through the upcoming Zurich Exchange platform, explaining how it works screen-by-screen. After outlining the functions, he runs through some examples of current APIs and the details you’ll see.

The API Exchange has been built with teams in mind. Sam and his team welcome your feedback so they can make the Exchange a truly interactive marketplace.

[29.30] Simone Novali, Italy BU

Simone outlines Zurich Italy’s experience with APIs and the lessons they learnt along the way. They started in 2015 with a drive to offer more, better digital services to customers and distributors. By the end of the journey, Italy will have almost 300 APIs that cover all the back-end functionalities.

• Think of APIs as lego bricks – start small and build
• Have managers on board to ensure capabilities
• Talk with experienced users (C4E team, other BUs) for advice
• Find and trust local partners to help develop APIs

• Plan migration carefully

   

[39:00] Oisin O’Farrell, Ireland BU

Oisin explains Ireland’s journey with MuleSoft, which started in 2001 when compatibility issues with legacy software made it complex and slow to maintain. In 2016, Ireland adopted MuleSoft to simplify, standardize and support digitalization.

Oisin’s lessons:

• Start small and simple but be meaningful
• Design, build and maintain your data model from the start
• Consider how to utilize the MuleSoft platform to support a more agile development methodology
• Define the principles of your APIs
• Ensure reusability
• Learn the technologies you use

• Plan to make mistakes – start with a small, low-risk pilot

   

[48:50] Useful links

• API products: www.suite.zurich.com/marketplace
• Guidance and best practice: www.zurich.io/api

• Register for early access to API exchange: www.zurich.io/yes

   

Does Zurich have experience building APIs to enable connectivity with non-web-based platforms such as the AS400 core system?

Oisin: yes, GI and Life perspective. Reach out to me.

Are there any data confidentiality requirements?

Yes. We have a proven platform approved globally for highly confidential data but that doesn’t absolve you of the responsibility of data confidentiality. You still need to gain approval and make sure that your API or interface is secure.

Are there any data confidentiality requirements?

Yes. We have a proven platform approved globally for highly confidential data but that doesn’t absolve you of the responsibility of data confidentiality. You still need to gain approval and make sure that your API or interface is secure.

What are the benefits of APIs over web services?

Mainly very clear standards and being more open. Web services have been around for a while and can be quite daunting, APIs are well understood and developers are familiar with them. They are open and ubiquitous as well as having many technical benefits.

What’s the recommended method for authenticating APIs?

There are a number of plans supported within the platform. GDP can help you determine which is most appropriate

Is there a preference between Azure and MuleSoft?

We’re happy for you to choose whichever you prefer, we will provide you with the support you need.

Small BUs don’t have developers, do you have this service and can you indicate budget required?

It's difficult to give a specific cost. We recognize that smaller teams don’t have the capability and if we have the demand over time we will grow the resources.

Very happy to have follow up conversations.