Guided paths for the work your teams already do. Each tutorial is a full story, from the first service to a running integration.
A complete path from the first service to a running integration that orchestrates remote systems. This is the story to start with when the project is still on paper.
Start the main tutorial
Design the API, attach security, and let OpenAPI come from the services themselves. One control plane for the APIs you expose.
REST API tutorialClinical and EDI traffic next to everything else. Destinations in the dashboard or a routing service of your own, no second stack.
HL7 tutorialStand up a gateway, assign keys, and let Cursor, Claude, and the rest of the clients call the services you already run.
MCP tutorial
Build requests as Python objects, unwrap incoming envelopes, and keep WS-Security in definitions. The protocol stays in the platform.
SOAP tutorialsThe same service, on a cron or an interval, with a history operations can read. Jobs live next to the APIs they call.
Scheduler tutorial
A GitOps path from a project on disk to a running environment. Services and config move together.
Deployment tutorial
Automate 365 and query SAP or Dynamics through OData from the same dashboard as everything else.
Microsoft 365 tutorialExpress business rules both sides can read, and test services without standing up a server.
Rule engine tutorialdef handle(self):
data = self.request.payload
# Business people wrote the rule, Python runs it
if result := self.rules.airport.match(data):
self.invoke('ops.rebook-passengers', result)Pick a tutorial above or schedule a demo to see how Zato fits your environment.