1. Introduction

This article explains how to expose B2B channels as an API. This article requires a prior understanding of REST.

Why does a customer need to expose B2B Channels?

• To provide different types of authentication/authorization (for e.g. Kerbos,OAuth2,JWT,OpenID), as of now B2B supports only basic authentication.
• To apply different threat protection policies to prevent malicious attacks (such as DOS, denied IP’s) on the applications.
• Protect your applications that also involve large and recursive payloads and SQL injections.
• To subject your API calls to prevent anti-virus scans.
• To Enable RESTful API enabled B2B communication.
• To avoid exposing native endpoint in cloud.
• If a partner in B2b cloud wants to use REST on top of their existing and wants to have more security on b2b communication

2. Pre-Requisites

• Create enterprise and partner in webMethods.io B2B cloud.
• Create Inbound channel and processing rule.
• Refer to WEBMETHODS.IO B2B TUTORIALS AND GUIDES

How to expose the B2B channel in API gateway?

         Login to API gateway and create an API with a B2B inbound channel endpoint.

1886×764 66.6 KB

 Add the resources and methods as shown below.

1896×609 50.2 KB

Select the methods as POST and pass the channel_id as the parameter. Copy the channel id from webmethods.io B2B -> channels page.

1894×694 62.1 KB

  Add the below method parameters for posting the EDI inbound message from the API Portal.

1496×579 41.2 KB

Policy Recommendations:

Run time Invocation from API Portal

After applying the above policies save the API and publish it to the API Portal.

1919×676 37 KB

After publishing to the portal and run the API by clicking the Try API button. In this example, we are providing the body content as below. (you should get response 200 OK)

1911×815 78.8 KB