Zato Blog

Open Source ESB, APIs, AI
and Cloud Integrations in Python

post 1 image
Salesforce connections are one of the newest additions to Zato 3.2, allowing you to look up and manage Salesforce records and other business data. To showcase it, the article will create a sample Salesforce marketing campaign in a way that does not require the usage of anything else except for basic REST APIs combined with plain Python objects, such as dicts.

Topics: API, Salesforce

post 2 image
Zato is a Python-based middleware and backend platform designed for integrating and building server-side systems. The platform belongs to a broader family of solutions that, depending on one’s background, will be known under the name of an integration layer, integration platform, service-oriented platform, enterprise service bus, API server, message bus, message queue, message broker, orchestration engine or similar.

Topics: Architecture, Documentation, API, Publish-Subscribe, Scheduler

post 3 image
Visual Studio Code offers excellent means to debug remote API servers without a need to ever leave your IDE. This post is a step-by-step guide describing the process of configuring your local VS Code instance for remote Python and Zato code debugging.

Topics: API, VSCode, IDE, Debugging, Tutorial

post 4 image
Zato is an integration platform and backend application server which means that, during most of their projects, developers using Zato are interested in a few specific matters that I am covering in this article.

Topics: API, Dashboard, Automation, OpenAPI

post 5 image
If you are on Windows, looking for an integration platform to connect your APIs, systems, applications, backend resources or mobile apps, I am happy to let you know that Zato now supports Windows natively - read on for more details on how to get started with it.

Topics: API, Windows

post 6 image
Building scalable, high-performance API and AI integrated environments requires a consistent vision and tenets to establish it on. From this article, you can learn how to design your own API and AI architectures based on what our vision is and how it is executed.

Topics: API, AI, Architecture

post 7 image
This Zato how-to is about ensuring that only API clients with valid SSL/TLS certificates, including expected certificate fingerprints or other metadata, can invoke selected REST endpoints. In this way, we are making access to the endpoints secure and, at the same time, we can guard against a class of faults related to the Certificate Authority infrastructure.

Topics: REST, Security, SSL-TLS

post 8 image
Even if most of new APIs today are built around REST, there are still already existing, production applications and systems that expose their APIs using SOAP and WSDL only - in today’s article we are integrating with a SOAP service in order to expose it as a REST interface to external applications.

Topics: SOAP, WSDL, REST

post 9 image
The seemingly simple zato --version command packs in several interesting details that are helpful in understanding what Zato version one currently uses - let’s find out what they all mean.

Topics: CLI