An overwhelming number of applications use REST API to ensure communication with other applications and services. In fact, we have a REST API of our own and most of our connectors are built on top of certain REST APIs, such as MailChimp, SugarCRM, Salesforce, Magento, and so on.
Typically, REST APIs are very fine-granular creatures composed of multiple GET-POST-PUT operations. With the help of some recent elastic.io functionalities like recipient list, content-based router or pass-through you can efficiently orchestrate multiple REST APIs, and that is due in no small way to the REST client.
The REST API integration component to fit ’em all
Our new REST API component – aka REST client – allows you to connect to and query virtually any REST API. So now, if you have an API but don’t have a connector for it, you can just take the REST API integration component, configure it appropriately and voilà, use it in the similar way as if it were an actual connector for the application of your choice.
From low-code to no-code
We trust that the REST API component will especially appeal to the users who either cannot code a full-blown connector on their own or are not that into coding full-blown connectors in general. In other words, this new integration component perfectly fits into the low-code/no-code philosophy of the elastic.io platform and we believe that someday, it might even replace the classic connectors development.
Read our documentation on the REST API component to learn what very few things you need to be able to use it and how to configure it properly.
The Local Agent: Beta testers wanted
We have already mentioned a few times that we have been working on the Local Agent – the service for a secure cloud to on-premises communication between applications, services, databases and so on.
Now we are finally opening it to beta testers, and you are invited to poke around it. If you are already an elastic.io user, please go to ‘Settings’ in the dashboard, click on “Agents” and then create a new agent.
If you are not registered on the elastic.io iPaaS yet, then please contact us via email@example.com and one of us will get back to you with further information.
Please NOTE: During the beta testing period, the Local Agent will be available for all pricing plans, regardless of whether your current plan includes it or not. After this period, it will be available only for specific plans (see our Pricing Plans for more info).
Introducing the ‘Edit’ option of data samples
If you are an active user of the elastic.io iPaaS, you are already pretty familiar with the concept of data samples. If you’re not an elastic.io user yet, you can imagine it the following way: When you create an integration workflow, you see immediately if you succeeded because the Integration Flow Designer shows you the results of your mapping with your own data. It queries the APIs and randomly chooses several data sets to test your workflows.
Now imagine you have a condition in your integration workflow, which none of the delivered data samples can meet. Or you happened to receive some incomplete data samples that miss a field here and there, whereas your workflow requires samples with all fields available. What can you possibly do?
The obvious answer would be – just edit the data samples however you need them. And now this has become possible on the elastic.io iPaaS:
Moreover, the available correction/edit options are conveniently suggested right in the editor window:
See for yourself how easy it is to make data samples dance after your pipe – just open your flows and hit ‘Edit JSON’.
And now, bits and pieces:
We have covered the main news on the elastic.io iPaaS, but there are also a few smaller ones.
We are finally introducing the localization and internationalization of elastic.io. Now you can choose in what language your instance of the elastic.io iPaaS (that is, of course, if you have your own instance) will have – from German through to Japanese.
Sorry to see you go, Look-up Tables
The introduction of JSONata has obviously made look-up tables look like a relic. In fact, they are completely redundant now, that is why we are deprecating them.
It doesn’t mean that your integration workflows built with look-up tables won’t work anymore – quite on the contrary, they will work an eternity, so to speak. But you won’t be able to create any new integration workflows with them, sorry! (not sorry)
The elastic.io API is dead, long live the elastic.io API
The wave of deprecations hit yet another element of the elastic.io iPaaS – and that is our Integration Management API. But no worries, not the Integration Management API per se. Just its first version. The second version is now fully-functional and the only default elastic.io API you can and should use.
If you’re still using the first version of the elastic.io Integration Management API, you should really migrate to the second version, but you have nothing to worry about yet. Despite its deprecation, it still works the same way as it did before. The ultimate end of life (if there is such a thing as ‘ultimate end of life’, of course) is planned at the end of the 1st Quarter 2018.
Though we still don’t recommend you to wait until March 31st, 2018 with the migration.
What to expect in the coming weeks:
Well, as for us, we certainly do expect our Local Agent to be released out of beta. But for that we need you, beta testers. So, please, allow us another reminder: Come and test the Local Agent.
Then we also keep on improving the experience with data samples. Next step will be adding the option to write your own data samples from scratch, without relying on any existing data.
Last but not least, soon we will support codeless connectors creation. You will have to wait to learn about the specifics, but for now, we can reveal that this will be done on the basis of Open API Specification (Swagger 2.0).
Stay tuned for more info.
In the meantime, why don’t you test the Local Agent … or … the REST API integration component 😉