Skip to content




API Explorer


Release notes

Martini Runtime

Martini Desktop

Martini Online

Feature requests

Bug reports

Creating a Gloop SOAP API

You can create a new Gloop SOAP API from scratch, or generate one from an existing definition. To learn how, read the steps below:

Create SOAP API from scratch

Create SOAP API from existing API file

Create SOAP API from WSDL

Create SOAP API from scratch

Create SOAP API from existing API file

Create SOAP API from WSDL

  1. Under your Martini package's code directory, right click where you want the .api file to reside. From the appearing context menu, select New > Gloop API. You will be presented with the Gloop API wizard.
  2. Choose Publish, then click Next.

    To consume, or to publish?

    Consume is for generating Gloop services that each call a provided API's endpoints. Publish generates an .api file for serving new or existing APIs in Martini.

  3. Enter the name of your API and then select New SOAP API as the type. Click Next.

  4. Choose your Gloop SOAP API's source.
    • Select None if you want to create your Gloop SOAP API from scratch.
    • Select Existing Gloop SOAP API if you want to clone an existing Gloop SOAP API. You will have to specify which Gloop SOAP API to clone by browsing its location or by dragging and dropping the .api file in the text box.
    • Select Existing SOAP API (WSDL) if you want to create a Gloop SOAP API from a given WSDL file. You can specify the source .wsdl file by dragging and dropping the file, browsing its location in the local file system, or by entering an HTTP URL.
  5. If you have selected None as the source in the step above, you can optionally click Next and specify the Gloop services that you will use to process requests and produce responses.
  6. Click Finish.

SOAPAction header

When making a request to a Gloop SOAP API, as specified in the SOAP specifications, the SOAPAction header value has to be wrapped in double quotes (") like so:

SOAPAction: "apis.service.HelloYouService"

Failure to do so will result in a SOAP fault response of:

<?xml version="1.0"?>
<soapenv:Envelope xmlns:soapenv="">
          <faultstring>Cannot resolve SOAPAction apis.service.HelloYouService</faultstring>
          <faultactor>Fault Actor</faultactor>