SOAP (Simple Object Access Protocol) is a highly structured protocol used, to exchange XML-based information when implementing Unimarket Web Services. Unlike the simpler POX protocol, SOAP relies on a WSDL (Web Services Description Language) to define the exact operations and data structures available.

Implementation Guide

To integrate using SOAP, your development team will typically use the WSDL to auto-generate the necessary client code for your specific programming platform (e.g., .NET, Java).

1. Technical Prerequisites

• Authentication Details: Contact Unimarket to obtain your Tenant Identifier, Integration Username, and Shared Secret.

• WSDL File: Download the official Unimarket WSDL from the Webservice Integration Documentation to identify the service operations.

• XML Schema (XSD): Reference the schema to identify the top-level request elements required for your specific integration (e.g., Budget Check or User Sync).

2. Message Structure

A valid SOAP message for Unimarket must contain:

1. SOAP Envelope: The outer wrapper for the message.

2. Authentication Header: Your credentials must be included within the SOAP header to be accepted.

3. Request Body: The specific uXML request element that conforms to the Unimarket schema.

3. Regional SOAP Endpoints

Messages must be sent as an HTTPS POST to the unsigned SOAP endpoint relevant to your region and organization type:

Pro-Tip: Testing with SoapUI

For initial testing and debugging, Unimarket recommends using SoapUI, a free open-source tool. By importing the Unimarket WSDL into SoapUI, you can quickly generate sample requests, input your credentials, and see the real-time XML response from the Unimarket servers without writing any code.

Comparison: SOAP vs. POX

While both use XML, SOAP is preferred for enterprise-level integrations where strict interface contracts and formal error handling are required. POX is often chosen for simpler, lightweight data-sync tasks.