Retrieving data from a source, ensuring it suits business requirements, and moving that data into a target data source is critical to any data strategy. Low-code tools can help create robust and flexible ETL processes that automate your data loading.
A typical IT task is moving data around and making it available for consumption. Many different approaches can be used to facilitate the movement of data. This post will take a deeper look into different data transfer options and how you can automate them.
The definition of a web service can differ between organisations. As a general concept, a web service is an application that provides services over a web protocol, such as HTTP. For the purpose of this article, we will refer to web services as APIs.
Sage Intacct is one of the largest cloud-based accounting systems, offering a web service to facilitate integrations. This post covers how you can consume the Sage Intacct web services with Linx. TLDR: Download the demo solution to fast-track your development.
OAuth 2.0 is becoming a popular alternative for application authentication. With Microsoft discontinuing Basic authentication and making OAuth 2.0 one of their new standards, many developers are sure to be in a situation where they need to change how they handle authentication for popular applications such as mailboxes, exchange services, and more. This article will briefly touch on OAuth 2.0, how it can be used, and an example of using it read mail from an Office 365 mailbox.
Developing applications in Linx follows common programming paradigms. This means that it will use variables, loops and if statements in a similar fashion to a traditional programming language. With this in mind, a recent update (6.4.1) introduced the Return function. The Return function is the new standard for returning values to the result of a function or to exit a function at any point. This post will go over what the Return function does and how it can be used.
This guide will take you through the steps to build and host an API using Linx. It will cover building a straightforward API to retrieve product data. You will be provided with the data, instructions for what tools to use, relevant scripts and all steps to get the API live. It will take about 20 to 30 minutes to complete all steps.
There is an understated art to building good APIs – ones that are easy to integrate with, have high operational availability, offer readily attainable performance insights, and are easy to maintain. But if you have ever had to build an API from scratch, there is no denying that it is hard – and it gets much more complicated when you aim to deliver a quality API.
