What SOAPless supports now, and what we are improving next
This page highlights what is available today and the areas we are focused on improving next. We update it over time based on real usage and customer feedback.
Available now
These workflows are already part of the product and ready to use today.
WSDL import and schema mapping
Register a WSDL endpoint and SOAPless maps operations, request fields, response fields, and faults into a REST-friendly surface.
SOAP to REST JSON proxy
Call SOAP operations with JSON over HTTP and receive structured JSON responses without hand-building XML envelopes.
Method controls per service and operation
Keep everything on POST, use the service default, or explicitly expose GET where it fits the operation and your client needs.
OpenAPI export and API Explorer
Generate an OpenAPI document for each registered service and inspect the resulting endpoints from the dashboard.
API keys and dashboard testing
Issue API keys, scope access by plan, and test operations directly from the dashboard before wiring clients into production.
In active development
These are the product areas receiving the most attention right now.
Better observability in the dashboard
Clearer latency, error, and request-level visibility so teams can understand service health without digging through logs.
Safer GET and cache-friendly read paths
More deliberate handling for read-like operations so GET exposure and downstream caching can be applied with less guesswork.
WSDL change review before refresh
Safer refresh flows with clearer visibility into added, removed, and changed operations before you apply updates.
Planned next
These are important roadmap themes, but they are not promises about exact release order.
Team workspaces
Shared access, teammate invites, and role-based administration for teams managing multiple SOAP integrations together.
Custom domains
Serve your REST facade on a domain you control instead of the default SOAPless-hosted endpoint.
Webhook notifications
Notify your systems when usage thresholds, key events, or service-level changes need attention.
WSDL 2.0 support
Broaden compatibility for teams that depend on WSDL 2.0 service descriptions.
Under consideration
These ideas are meaningful to customers, but they need more validation before we commit them to the near-term roadmap.
Private network connectivity
A way to reach SOAP services that are not publicly exposed, including systems behind VPNs or internal networks.
MTOM and large attachment handling
Support for SOAP services that exchange large binary payloads such as PDFs, images, or other documents.
GraphQL gateway options
An alternate query interface for teams that want a GraphQL layer on top of existing SOAP operations.
Want to influence what we build next?
The roadmap moves most when customers show us where SOAP integration work is still too painful.
Share feedbackStart with what is already available
Create an account, register a WSDL, and test the REST facade before you commit client traffic to it.
No credit card required for the free plan.