Alumio's HTTP connection features work perfectly to create connections with Rest (also known as RESTful API and stands for Representational State Transfer) and ODATA (the Open Data Protocol).

Configure HTTP clients and use them to interface with HTTP endpoints using HTTP-compliant methods. Requests can be expanded to contain post data. Authentication methods like OAuth 2.0 can be configured on an HTTP client.

PDO is a lightweight abstraction layer for accessing databases. 
‍
Configure database clients  to fetch and post database data, execute stored procedures, etc.  Alumio offers database drivers for Oracle, IBM, CUBRID, MS SQL Server, Firebird, Informix, MySQL, PostgreSQL, SQLite, ODBC, and DB2.

SOAP support is an extension upon  Alumio’s HTTP elements, including authentication. This protocol may not always be the leading protocol, but it is still widely in use. 

Configure clients to connect to a SOAP service to fetch and post data. Alumio offers a solution to adapt to the inherent differences between SOAP services, like adding a custom authentication envelope or changes to the message structure. 

Filesystems are interfaced with using Flysystem, which is an abstraction layer to standardize filesystem interactions agnostically. 

Configure filesystems to read and write files on services like FTP, SFTP, AWS S3, HTTP, etc. Filesystem interactions are performed stateless. 

Alumio can receive triggers to start routes from external endpoints.  Webhooks allows systems to send automated messages or information to Alumio. It’s a powerful way to automatically push data from one app to another. 

Alumio can function as an HTTP proxy between two endpoints for HTTP requests. Instead of sending HTTP messages directly to an endpoint, messages can be sent through Alumio. Alumio will forward the requests to the endpoint and return the response that it receives as if the endpoint was called directly. This gives every existing connection that uses Alumio’s HTTP Proxy the logging capabilities Alumio offers.