SOAP APIs

Many ERPs and HR/payroll systems expose their data only through SOAP web services: XML envelopes, WSDL contracts, custom authentication headers and order-sensitive payloads. SOAP sources are served by RWS Connect: we build a managed pipeline that extracts from your SOAP services and exposes them through the RWS Connect API, a simple REST API that your integrations extract from like any other modern API.

​

When to use

• The source system only offers SOAP web services (common in HR, payroll and fiscal ERPs)
• Getting one complete record requires calling several SOAP operations and combining the results
• The service returns deeply nested XML that would be painful to consume directly
• You need both a scheduled feed of changes and a backfill of historical data

​

How it works

1. RWS Connect calls the SOAP operations for you, with authentication, pagination and retries included
2. The pipeline combines and flattens the results: data from multiple operations is joined into complete records, and nested XML becomes flat columns
3. Your integration extracts the table through the RWS Connect API, like any other REST source

The pipeline runs on the agreed schedule (typically daily) and can also backfill history over a date range, so your table starts complete instead of empty. Everything the platform offers for API extractions works unchanged: pagination, dynamic parameters, business rules and scheduling.

​

What you provide

​

Requesting the connector

Email connect@rwsintegration.com with the items above to open a ticket.

​

How your data appears

• One table per dataset, named as agreed in the ticket
• Nested XML structures flattened into snake_case columns
• Each column is prefixed with the operation or endpoint it came from (for example employees_name and contracts_start_date), and every record is delivered as a single flat JSON object (see Column prefixes)
• Every run adds a snapshot stamped with the extraction date, so history is preserved. A one-time backfill can load past periods
• Standard columns on every table: extracted_at, extraction_date, extract_start_date_parameter, extract_end_date_parameter

​

Next steps