Click SOAP above the Template Editor to select this format type.
In theory, if a buyer specification contains a sample request to the buyer API, you can copy it to the Template Editor to simplify mapping process. However, in practice, sample requests in specifications rarely contain all the necessary fields. So it is recommended to map all the fields manually.
First, check if your buyer specification includes SOAPAction element. If yes, it should be configured as a Header in Step 1 using the following instructions:
1. Go to the Step 1 and navigate to Authentication method block.
2. Select Header authentication method:
3. Enter SOAPAction into the Test Header Name field and SOAP Action value into the Test Header Value field (this can be either a link or a text message, depending on buyer specification):
Click Save and continue as soon as you are done.
XML Namespace Attribute
Find the xmlns (XML namespace) attribute in buyer specification that contains the link provided by the Buyer. The tag, which contains this attribute, can have various names according to the buyer specification. In our example, it is named Request.
Add the tag that contains xmlns attribute with a buyer link to the Template Editor:
In SOAP, all mapping is performed inside this tag with xmlns attribute.
Usually, buyer specification contains XML SOAP request sample. The structure of the code entered inside the tag with xmlns attribute (Request tag in our example) must be the same to the structure inside the Body tag of the buyer sample request.
Read more about SOAP.
SOAP Mapping Flow
As soon as SOAPAction (if specified) and XML namespace attribute have been configured, you can perform mapping of all fields and inputs from buyer specification. SOAP is based on XML, so the SOAP mapping flow is similar. Follow XML mapping instructions to map all necessary fields and inputs.
It is recommended to click Save at the bottom of Step 2 - Map API Inputs periodically to save your mappings.
As soon as you are done, click Save and Continue to save your mappings and proceed with the next step.
As soon as all fields are mapped for ping request, it is recommended to go to Step 3 and then to Step 4 in order to make all possible testing, and only after that proceed with mapping Fields & Inputs for Post request. This flow allows avoiding random lead sales because of sending the post request to the buyer.