Resources Sample File: MicrosoftGraphTemplate.lsoz (65.8 KB) (download) API Reference: More information on the specifics of authentication can be found in the Microsoft Graph API reference documentation. Microsoft offers a RESTful web service named Microsoft Graph API. This tutorial shows you how to integrate with the Microsoft Graph API and Linx, a low-code development tool.
Using a low-code platform as the back-end for a single page application (SPA) is a nice combination — the SPA can be hosted anywhere, the API is quick and easy to develop, and they can evolve independently of each other e.g. if you need a native app just develop the UI and use the same API.
SOAP, being a mature technology, has an extensive and often differently interpreted standard set. This makes it an excellent tool for corporate users to manipulate data into their precise requirements and technology stack. However, for public consumption, this causes issues that sometimes are difficult or impossible to solve without changing code. A good example here is that SOAP is allowed to define the same type in some standard interpretations in different XSD files.
You would think in the Internet age, primary sources for a widely discussed event — one that’s helped define cloud computing and today’s cascading digital transformation of enterprises — would be easy to track down. The original footprint must be somewhere. But that’s not so in the case of the arresting “API Mandate,” perhaps better thought of now as the API Mandate or API-First Mandate.
If you’re a SaaS company, it is impossible not to tackle the topic of integration. Whether you’re a small software business or a large, established tech enterprise with several SaaS products, every commercial conversation is highly likely to involve the question “Will I be able to sync data from your application with my CRM / ERP / Finance / Marketing” – you name it.
Photo by Tima Miroshnichenko from Pexels
