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.
We will implement some web methods, which will be useful for creating a messaging client. However, the following items fall outside the scope of this sample.
Seven years ago, we announced Linx 5, a release specifically designed to modernise and commercialise an internal tool we had been using with our enterprise customers for the previous 15 years. By all accounts, Linx 5 was a huge success with our customers and partners. With Linx 6, we’ve built on that success with new features, a streamlined UI, and a new diffable file format – something our customers have been clamouring for.
RealWorld is a popular open-source project known as the mother of all demo apps. It is an exact clone of Medium.com (called Conduit) and can be built using any front-end and back-end. This article will share the journey to replicating the RealWorld REST API (Conduit) from scratch using Linx, a low-code developer tool. All stacks that integrate with Conduit will integrate with the newly created API. Technologies and tools used to develop RealWorld API: Notes
REST and (the newer) GraphQL APIs are the core technologies behind the vast most of today’s integrations. These APIs allow external developers to tap into the functionality of the major platforms and build in their custom functionality to suit their needs. The fundamental difference is that REST is an architectural design framework based on HTTP, while GraphQL is a query syntax that is not transport-dependent.
APIs are created so that users can use them as a bridge to connect to applications and services. There are thousands of APIs available for consumption, and each API is unique. But it’s really easy to consume APIs to extend the capabilities of your Linx apps, even complex ones that require OAuth 2.0 tokens. Let us show you how with a real-life example.
