News KrakenD CE v2.7 released with better rate-limiting and security options

Enterprise Documentation

Recent changes

You are viewing a previous version of KrakenD Enterprise Edition (v2.3) , go to the latest version

SOAP integration

Document updated on Feb 15, 2023

SOAP integration

The SOAP integration is the ideal tool for those companies that rely on SOAP services and would like to have an option to modernize their interface for the end-user.

KrakenD has the native capability of dealing with multiple encodings, like XML or JSON, and transforming from one to the other transparently before returning the content to the user. In addition, the SOAP integration adds the possibility to craft the body and XML content you will send to a SOAP service, injecting dynamic variables from places like the body sent by the user, headers, query strings, or parameters of the URL.

You can afterward manipulate the responses back to get the desired output, regardless of the end user’s encoding or method.

The SOAP integration introduces templates to craft the body sent as an underlying SOAP XML contract to the server, while the end-user doesn’t see any of that. You can decide to keep the SOAP response modified or “as is”, return JSON content, or another encoding.


To use the SOAP integration, you need to:

  • Decide what content type you are going to return to the user (by default JSON) in the output_encoding.
  • Write the SOAP XML request you will send for this endpoint
  • Inject any variables you need in the template

For example, you want to return json content (output_encoding) and send to SOAP the body (template) on each request:

    <User>{{ .req_params.User }}</User>

The {{ .req_params.User }} is an injected value from the URL.

The different configuration options of the SOAP integration are:

Fields of SOAP Template modifier
* required fields
Minimum configuration needs one of: path , or template

The Content-Type used in your template, and that will be sent to the SOAP server. This is not the content-type the end-user sent in the request.
Examples: "application/xml" , "text/xml"
Defaults to "text/xml"

When true, shows useful information in the logs with DEBUG level about the input received and the body generated. Do not enable in production. Debug logs are multiline and designed fore developer readibility, not machine processing.
Defaults to false

The path to the Go template file you want to use to craft the body.
Example: "./path/to.xml"

An inline base64 encoded Go template with the body XML content you want to send to the SOAP service. This option is useful if you don’t want to rely on external files and embed the template in the configuration.

Template definition

When you write the content of your body, you do it in a template. The template engine parses the content using the Go text template language (similar to Helm, Kubernetes, and other systems).

You can insert variables with the format {{ .variable }} that will replace the placeholder with the corresponding value.

The following variables are available in the template you will use to construct a body:


It contains the data sent by the user in the body request. You can reuse the body of the user sent in several formats, to compose the final body you will send to the SOAP server.

The .req_body is initially empty unless the following requirements are met:

  • The template has at least a .req_body declaration
  • The Content-Type is declared in the input_headers of the endpoint. The content type is necessary to determine how to parse the request body and make it available to the template. This is not the content_type configuration option you will send to the SOAP server. The following content types are the only ones that will work (otherwise, there will be an error):
    • application/json
    • application/xml
    • text/xml
    • application/x-www-form-urlencoded
    • multipart/form-data
    • text/plain

For instance, a user request like:

$curl -XPOST -d '{"foo": "bar"}' -H'Content-Type: application/json' http://localhost:8080/hello

Allows you to use in a soap template, which will translate into bar.


It contains all the parameters you have declared in the endpoint as {placeholders}. To access the parameters, use the first letter capitalized.

For instance, an endpoint defined like this:

  "endpoint": "/foo/{bar}"

Allows you to use in a template .req_params.Bar and contains the value of the request in {bar}.


It contains all the headers allowed in the endpoint, not the ones sent by the user. It means that the endpoint needs to declare in input_headers each header you would like to access. For instance:

  "endpoint": "/foo/{bar}",
  "input_headers": ["X-Header"]

Allows you to use in a template .req_headers["X-Header"]. Notice that we are accessing differently as the header contains -, and that is a minus sign on the template.

When input_headers is set to ["*"], all headers sent by the client are in the variable, although this practice might lead to potential security threads and is discouraged. Add only those that you will actually use.


It contains all the query strings allowed to pass in the endpoint. As with headers, the endpoint must declare the list in input_query_strings. For instance

  "endpoint": "/foo/{bar}",
  "input_query_strings": ["query","limit"]

Allows you to use in a template .req_querystring.query or .req_querystring.limit.

When input_query_strings is set to ["*"], then all query strings sent by the client are in the variable, although this practice might lead to potential security threads and is discouiraged.


The path that KrakenD will use to connect the SOAP server. It matches the url_pattern of the configuration.

SOAP integration example

Let’s show how this works with a testable example. We have a public SOAP service that returns information about a country, and when we make the right POST request, it returns the following content:

<Envelope soap="">
    <CountryFlagResponse m="">

What we want to achieve with this example is that our end-users receive this content as (method GET + JSON + transformation):


You can reproduce this test with the following krakend.json configuration that is explained below:

  "$schema": "",
  "version": 3,
  "endpoints": [
      "endpoint": "/country/{country}",
      "method": "GET",
      "backend": [
          "host": [""],
          "url_pattern": "/websamples.countryinfo/CountryInfoService.wso",
          "method": "POST",
          "encoding": "xml",
          "extra_config": {
            "backend/soap": {
              "path": "./soap_flag_request.xml"

          "target": "Envelope.Body.CountryFlagResponse",
          "mapping": {
            "CountryFlagResult": "flag_url"
          "deny": [

The content of the external soap_flag_request.xml file is:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="">
    <CountryFlag xmlns="">
      <sCountryISOCode>{{ .req_params.Country }}</sCountryISOCode>

When we start the server with access to these two files, we get beautiful JSON content from a dynamic SOAP request. These are the important takeaways from this configuration:

  • The output_encoding defines how you would like to offer the content to the end user. As the configuration does not specifies it, the default json prevails, but we could still return XML or RSS.
  • The host and the url_pattern define the SOAP endpoint.
  • The method we are sending to the SOAP service is a POST, but we allow a GET to the end-user, e.g., GET /country/US
  • The path defines where the external template is, using a relative dir ./ based on KrakenD’s working directory, but it can also be an absolute path.

Finally, there are a few additional basic manipulation options, that strip undesired content:

  • target traverses the response to a specific path and ignores everything else.
  • mapping renames the field to something friendlier
  • deny prevents undesired fields from showing up

As you can see, there is a variable {{ .req_params.Country }} in the template that the integration replaces by the value of the parameter in the request URL /country/{country}. Notice that the first letter in the template is in upper case.

To summarize, the host receives a POST request with the crafted body, and all the variables replaced, despite the user sending none. The target option tells KrakenD that the starting content is after traversing the XML in the path Envelope.Body.CountryFlagResponse, ignoring everything else. After finding the content, we finally renamed CountryFlagResult to flag_url, and the end-user received the response as we designed.

Helping your SOAP development

While working with the SOAP integration, you might find it useful to set the debug flag to true. This flag (that you should not use in production) outputs the following information in the console (when the debug level is DEBUG):

  • All the variables available in the template
  • The final generated body, after compiling the template and injecting the variables
  • The content type to send to the SOAP server

For instance:

2023/02/15 14:20:28 KRAKEND DEBUG: [BACKEND: /websamples.countryinfo/CountryInfoService.wso][SOAP] Template variables:
  "req_headers": {
    "Accept": [
    "User-Agent": [
    "X-Forwarded-For": [
    "X-Forwarded-Host": [
    "X-Forwarded-Via": [
      "KrakenD Version 2.1.2-ee"
  "req_params": {
    "Country": "DE"
  "req_path": "/websamples.countryinfo/CountryInfoService.wso",
  "req_querystring": {}
2023/02/15 14:20:28 KRAKEND DEBUG: [BACKEND: /websamples.countryinfo/CountryInfoService.wso][SOAP] Generated content-type: text/xml
2023/02/15 14:20:28 KRAKEND DEBUG: [BACKEND: /websamples.countryinfo/CountryInfoService.wso][SOAP] Generated body:
 <?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="">
    <CountryFlag xmlns="">
 2023/02/15 14:20:28 [AccessLog] | 200 | 151.883ms | | GET      /country/DE

Use the flag for faster development!


Unresolved issues?

The documentation is only a piece of the help you can get! Whether you are looking for Open Source or Enterprise support, see more support channels that can help you.