API Protocol Guide

Opsalis supports 6 API protocols. Your existing API works as-is — our handler bridges any protocol to our universal format. Consumers never need to know what protocol you use.

🌐 REST / OpenAPI The standard for web APIs. Resource-oriented design with HTTP verbs and JSON payloads. Learn more → GraphQL Query exactly what you need. Client-driven queries with strong typing and introspection. Learn more → 🏢 SOAP Enterprise XML web services. Strict contracts, WS-Security, and transaction support. Learn more → gRPC High-performance binary RPC. Protocol Buffers, HTTP/2, and bidirectional streaming. Learn more → {} JSON-RPC Simple JSON remote procedure calls. Lightweight, transport-agnostic, and easy to implement. Learn more → </> XML-RPC The original XML remote calls. Simple, well-understood, and widely supported since 1998. Learn more →

How Opsalis Handles Protocols

Regardless of which protocol your API uses, the Opsalis handler automatically bridges it to our universal OpenAPI-based consumer interface. API owners never change their code. Consumers always get a clean, consistent experience.

Owner side: Install the handler, point it at your existing server, upload your spec file (OpenAPI YAML, GraphQL SDL, WSDL, .proto, or method list). That is it — zero code changes.