FAQ — SOAP-2-REST by Specaria

Does it replace my API gateway? No. SOAP-2-REST complements your existing gateway. Your gateway keeps doing what it does today — authentication, rate-limiting, traffic management, WAF — and SOAP-2-REST sits alongside it, purpose-built to expose a REST surface on top of your SOAP estate.

What gateways and load balancers does it work with? The product ships connectors for common load balancers (F5 BIG-IP, Citrix NetScaler, HAProxy, nginx, Kemp, A10 Thunder, Radware Alteon) and API gateways (IBM DataPower, Layer7, webMethods, Akana, TIBCO Mashery, Oracle API Gateway). A generic-HTTP receiver works with any gateway, application server, or appliance that can emit accessible HTTP traffic logs — so you're not blocked if your edge isn't on the list.

Where does my data live? In your VPC. SOAP traffic, request and response payloads, archives, learned examples, and the metadata database all stay in your infrastructure. The vendor only ever sees a license heartbeat and update-channel metadata — never your traffic or payloads.

Do I have to write transformations or mappings? No. The platform generates a deterministic, full-field SOAP↔REST mapping from each WSDL automatically — every element, attribute, and optional field. There's no proprietary transformation language and no per-service scripting. When a business rule requires it, you can override field-by-field in the UI.

Does it go both ways — REST→SOAP and SOAP→REST? Yes. Publish exposes a SOAP backend as REST + OpenAPI. Consume presents a SOAP facade (WSDL) in front of a backend that has already migrated to REST — so legacy SOAP clients keep working while you modernize the backend.

Is the generated OpenAPI v3 standards-compliant? Yes. It validates against the OpenAPI v3 specification and imports cleanly into mainstream developer-portal tools, SDK generators, and AI-agent toolchains. Your conversion preferences (field casing, null handling, error shape, and so on) are reflected in the generated contract.

Which SOAP versions and XSD features are supported? SOAP 1.1 and SOAP 1.2, document/literal (wrapped and bare) and rpc/literal, and full XSD type coverage — complex types, choice/sequence/all, nillable and optional fields, attributes and mixed content, substitution groups, xsi:type polymorphism, enumerations, patterns, and wildcards. SOAP faults are normalized into a deterministic REST error shape (including RFC 7807 if you choose it).

What about Hebrew, RTL, and non-English locales? UTF-8 end to end, with correct right-to-left rendering (including Hebrew and Arabic) and per-tenant timezone and locale. Operator UI strings are localized; payload content is passed through unchanged.

How much traffic can it handle? It's engineered and load-tested for a ~1M-calls/day baseline (~12 rps sustained, ~100 rps burst), with configurable timeouts and retries and a 30 MB payload ceiling. Dashboards stay sub-second even across large estates.

How is access controlled? Role-based access control (admin / operator / reader) mapped from your identity provider's groups, with Google IAP, Azure AD, and standard SAML / OIDC supported at GA. There's no public endpoint, and every change is captured in an audit trail.

Can I run it air-gapped? Not at GA. v1 requires outbound HTTPS to the Specaria platform for license validation and the update channel. A generous offline grace period covers transient connectivity loss. Fully air-gapped deployment is a post-GA bespoke engagement.

How is it deployed? GCP-native, a Kubernetes / OpenShift Helm chart, a GCP Marketplace listing, or a standalone Docker Compose stack — all running in your VPC. VM images and additional cloud-native ports are on the post-GA roadmap.

How do I try it? Start a 45-day full-feature trial — no credit card, every feature, unlimited services during evaluation. Email sales@specaria.io.

---

For deeper technical answers, see the public knowledge base.