In this article

Overview

Proxy endpoints allow users to access your APIs and third-party APIs. You can define the HTTP methods for your endpoints and apply the appropriate authentication method.

You can:

• View the list of endpoints for the proxy.

• Create an endpoint.

• View and edit the settings of an endpoint.

• Delete an endpoint.

• Manage security policies to control access to the endpoint.

Endpoint Certificates

Third-party endpoints often have unsigned, self-signed, or expired certificates. Typically, an API will not execute if it encounters a certificate in one of these three statuses. The status of the certificate is beyond the control of an API developer, so if you trust the endpoint, it becomes an inconvenience for the API to fail. Proxies now support the ability to trust all endpoint certificates. You now have the option to choose an endpoint to trust all certificates when you create an endpoint in a Proxy.

SOAP Endpoints

Legacy SOAP services are still prevalent on the web. Enabling SOAP web services in REST APIs provides allows you to take advantage of these services in your REST API endpoints. You can use a Proxy to connect to a SOAP web service and apply API policies against it. In the Create Endpoint dialog, you can easily define parts of the SOAP payload to be dynamically provided by an incoming query parameter or header from the request to execute the Proxy endpoint. This capability enables you to take advantage of the SnapLogic server for your SOAP endpoints and expose them to REST clients.

Benefits

Listed are the benefits of publishing Proxies on your Developer Portal to expose SOAP endpoints:

• Developers now have access to more user-friendly REST APIs.

• The transition from SOAP to REST improves overall integration efficiency and performance.

• The APIM solution provides a centralized platform for managing and monitoring the APIs.

How it works

The Proxy API always treats the SOAP endpoint as a POST call. To turn the SOAP envelope into an HTTP service, the endpoint requires the payload the user wants to submit. This is accomplished via the SOAP parameters. These are added to the Proxy endpoint URI as a query parameter. The response is returned as a REST response. Because you might want to know the definitions of all your existing SOAP endpoints, you can compile them in one XML file. The endpoints broadcast the SOAP XML payloads for the client.

Order of Precedence

When calling a SOAP endpoint, the data is processed according to the following order:

1. Request Body

2. Headers

3. Query Parameters

Learn more about how to expose your SOAP endpoints as REST calls in this example.

Prerequisites

• Org Admin permissions

Viewing the List of Endpoints

To view the list of endpoints for a Proxy:

1. In SnapLogic Manager, go to API Management > API Manager.

2. In the API Manager, go to the APIs & Proxies tab.

3. Set Filter by Type to Proxy and click Search.

4. Click the Proxy's name in the list.

5. Go to the Proxy Endpoints tab.

Open

Creating an Endpoint

To create an endpoint:

1. In the API Manager, open a Proxy for editing, then go to the Proxy Endpoints tab.

2. Click to open the Create Proxy Endpoint dialog.

3. Configure the new endpoint:

   Open

   

Editing an Endpoint

To edit an endpoint:

1. In the API Manager, open a proxy for editing, then go to the Proxy Endpoints tab.

2. Click the endpoint's name in the list.
   
   

   Learn more: Proxy Endpoint Details.

3. To edit the proxy details, click the Edit Details button.

   Note: You can update only the URL and HTTP Method(s) of the endpoint.

4. To apply security policies to the endpoint, click the plus icon ( ) below the View Applied Policies button.

Deleting an Endpoint

To delete an endpoint:

1. In the API Manager, open a proxy for editing, then go to the Proxy Endpoints tab.

2. Check the box for the endpoint to delete.

3. Click the trash icon ( ). The Delete confirmation message appears:

4. Click Delete.

5. Verify the deleted Assets by navigating to the Manager Recycle Bin for your Org.

6. To delete forever:

   1. Select the endpoint.

   2. Click to delete it permanently from the Manager Recycle Bin.

REST to SOAP Tutorial

In this tutorial, we will complete the following tasks using SnapLogic APIM:

• Create a REST endpoint for our SOAP service

• Expose the SOAP service to our API consumers

• Demonstrate how to call the API

For example, the following SOAP envelope, http://www.dneonline.com/calculator.asmx, performs a multiplication operation for two variables. To use our SOAP to REST service, supply the SOAP envelope to access the service. We supply the variables that will be parameterized into query strings key-value pairs.

Here, the variables are n1 and n2, which must be integers.

The resulting REST endpoint looks like this:
https://cloud-dev-fm.snaplogic.io/gateway/Multiplier/Multiply?n1=xx&n2=yy

Where xx and yy are the specified integers.

The query parameters n1 and n2 are the key-value pairs that represent the numbers that will be multiplied by the SOAP service. The REST API response returns the product.

Create a REST endpoint for a SOAP service

We start in APIM by creating the API Proxy that generates the REST endpoints for the SOAP service.

1. In API Manager, click to add a new proxy.

2. In the Create Proxy wizard, click Create Empty Proxy.

3. Name the proxy, provide a description, enter tags, and click Create with endpoints.

    

4. In the Create proxy endpoint dialog, add endpoint details:

   1. Name the endpoint and add the URL.

   2. Click REST to SOAP, then enter the SOAP envelope.
      Tip: You paste the payload in the window instead of typing it.

   3. Click Create.

5. In the Endpoint URLs screen, do the following:

   1. Using the Snaplex picker, select the server to run the Proxy API. Here, we selected cloud-dev.

   2. Copy the endpoint URL.

   3. Click Close

Expose the SOAP service to API consumers

In this part of the tutorial, we expose the SOAP service by publishing it on the Developer Portal.

1. In the Proxy tab, click Generate Specification,

   1. Select specification type: (OAS 2.0/3.0)

   2. Select format: (JSON/YAML)

   3. Click Publish.
      For this example, we selected OAS 2.0 for the specification type and YAML for the file format.

2. In the Publish dialog, select File from Proxy, and then choose the generated file from the dropdown picker.

   1. Click to open the Swagger specification editor.

   2. In the specification, add the following field to the specification, paste the endpoint URL, then edit as shown in the following image:

      Here both the host and parameters are specified.

   3. Click Save.

   4. Enter the remaining publication details in the dialog, and publish the Proxy.

Demonstrate how to call the API

1. Navigate to your Developer Portal and view the Proxy.
   Note that the SOAP service displays as an API with a REST endpoint.

2. To test the proxy, call the API using your method of preference and specify the query parameter:
   https://cloud-dev-fm.snaplogic.io/gateway/Multiplier/Multiply?n1=xx&n2=yy

   CURL command example:

   curl -X 'GET' \ 'https://cloud-dev-fm.snaplogic.io/gateway/Multiplier/Multiply?n1=5&n2=300' \ -H 'accept: application/json'

    

   Response:

   {"Body":{"MultiplyResponse":{"MultiplyResult":"1500"}}}%   

The following repeating video demonstrates how an API consumer would test the service using the Try it out functionality available in the Developer Portal: