Connector
SOAP API → your warehouse
WSDL, envelopes, namespaces, session-token authentication and pagination that works differently on every operation. Nobody wants this work. We do it.
What it costs
Two kinds of line. The connector is the technical connection to this source, charged once. The data models are the datasets you actually asked for, priced by type.
- Build
- Base Connector · Complex source · incl. 3 data models
- Price
- See the price list
Data models customers ask for on this kind of source
Three Simple ones come with the Base Connector. These are what tends to get added.
| Data model | Typical type | API resources it usually needs |
|---|---|---|
| Shipments | Advanced | GetShipments, GetShipmentDetail, GetStatusCodes |
| Invoices | Custom | GetInvoices, GetInvoiceLines, plus reconciliation |
| Reference data | Standard | GetLocations, GetServiceTypes |
Illustrative, not a quote: the type is assessed per customer from the API's own documentation. Note the last column — those resources are included in the data model price, not charged separately, and their raw data lands in your warehouse too.
What decides the type
- Session-token authentication that expires mid-run
- Pagination that differs per operation, or silently truncates
- Deeply nested XML that has to be flattened without losing meaning
- No incremental capability, so change detection happens on our side
What you get
- A connector handling the WSDL, the envelopes and the session lifecycle
- Documented flattening from nested XML to warehouse tables
- Client-side change detection where the API has no incremental support
- Historical backfill, executed in full and resumable
- Monitoring, alerting, runbook, infrastructure definitions and source code, in your accounts
Why a SOAP interface is a Complex connector
No catalogue will ever cover it. A SOAP interface belonging to one industry vendor with a few hundred customers is not worth a connector company’s engineering time, and it will still be the system of record in five years.
The work is genuinely harder than REST, and we price it accordingly rather than pretending otherwise:
- Authentication is often a login call returning a token that expires. Re-establishing it mid-run without losing checkpoint state is real engineering.
- Pagination is frequently per-operation, undocumented, and sometimes capped without saying so.
- Schemas are nested several levels deep, and the nesting carries meaning that a naive flatten destroys.
- Incremental sync usually does not exist, which means detecting change on our side.
What we will not do
Quote a Complex connector from documentation that does not exist. If the API has no specification and we cannot call it, we will offer a paid two-day investigation, credited in full against the build — rather than a fixed price we cannot stand behind.
Get an estimate for soap api → your warehouse
Send the documentation link. You get a complexity tier, a recommended architecture, a fixed price and a delivery window — free, usually the same day. If a vendor connector would serve you better, we will say that instead.
Get an estimate