Expose Integration Flow Endpoint as API and Test the Flow
Define the endpoint of the integration flow developed in the last tutorial as an application programming interface (API).
Overview
You will learn
- How to define and expose an integration flow endpoint as an API
- How to assign a policy to your API
Prerequisites
Prerequisites
Steps
Context
In this tutorial, you will define the endpoint of the integration flow developed in the last tutorial as an application programming interface (API).
Intro
In addition, you will assign a policy template to the API to define how the API is called. A policy defines, for example, how an API can be called. In this tutorial, you assign a policy that defines an authentication of the API according to OAuth 2.0 client credentials grant. It is a secure way to control access to an API.
After you’ve performed these steps, finally, you will call the API to fetch the product details.
In this step, you copy the endpoint address of the integration flow.
Open your integration flow.
In the Deployment Status tab of the property sheet, choose the navigation link.

Access Deployed Artifact In the Endpoints tab, choose the Copy icon.

Endpoint URL
In this step, you define and expose an integration flow endpoint as an application programming interface (API).
- To provision the API Management capability, go to Settings > Runtimes and choose Activate. The provisioning might take a few seconds to complete. After the provisioning is complete, refresh your webpage.
The page is available only if you’re provisioning the capability as a first-time user. If API Management is already provisioned in your subaccount, continue with the next step.
Go to Configure > APIs and choose Create to create an API proxy.
On the Create API dialog, next to Select, select URL and specify the following parameters:
IMPORTANT: Paste only the endpoint URL until
/http/products. Otherwise, the scenario will not run correctly.
| Parameter | Settings
| :------------- | :-------------
| URL | Paste the integration flow endpoint address you have copied in **step 1**. It ends with **`/http/products/details`**. Paste the endpoint URL only until **`/http/products`** instead of **`/http/products/details`**.
| Name | **`RequestProductDetails`**
| Title | **`Product Details API`**
| API Base Path | **`/products`**

Select **Create**.
On the landing page, go to the Resources tab and choose Add.

Add resources In the field Tag, enter
Product Details, and in the field Path Prefix enter/details.
Add details Under Operations, delete all tabs except the POST tab and choose OK.

Add operations The API resource is displayed.
Choose Deploy to create and activate the API proxy for your integration flow.

Deploy Choose the POST operation to display more details on the API. A default API definition in Open API specification format is also generated.
To update the generated API definition in Open API format, choose Edit > Edit in API Designer.

Edit API designer The API designer opens.
In the editable section on the right part of the screen, make the following changes.
Change the key Payload in line 37 to
productIdentifier. Then, add a new row after type with the following key-value pair:example: HT-2000TIP: Instead of copying the example, type it manually.

change product identifier before 
change product identifier after Choose Save.
Choose
RequestProductDetailsand then the Resources tab. Then, choose Edit > Edit in API Designer.Now choose the POST request. You notice the API changed, in particular, the request body now contains one element with a product identifier.

Resources Tab API Changes When you choose Try Out and then Execute, since no authentication details have been configured, you get an error message with error code 401 (not authorized). We will fix this error in the next steps of this tutorial.

Error message With this step, you have successfully created an API proxy for your integration flow and generated an API documentation for your REST API in
OpenAPIformat.
In this step, you’ll copy the client ID, client secret, and token URL from the service key that you automatically generated in your SAP BTP account. See Set Up SAP Integration Suite Trial.
In your SAP BTP subaccount, navigate to your service instance page. Choose Services > Instances and Subscriptions.
Under the Instances section, look out for the service instance that was created. Choose the key under the Credentials column to open the service key.

view key TIP: In trial accounts, the default name that the booster provides for the service instance is default-it-rt-integration-flow. In free tier accounts, the instance name is user defined.
Copy the values of the
clientid,clientsecretandtokenurlparameters. These are the credentials that you later use to make a request to your integration flow.
Copy clientid and clientsecret
In this step, you assign a policy template to your API to specify authentication details for the API call. In particular, you use a policy template that defines that the caller of the API authenticates itself using OAuth 2.0 client credentials grant.
This grant type works in the following way: In a first call, the API client provides the values of clientid and clientsecret (from the service key generated in step 1) to a token service (the URL of the token service is also contained in the service key definition). The token service provides an access token to the API client. In a subsequent call, the API client calls the integration flow endpoint providing the access token. If the access token is valid, the API client is authorized to call the integration flow.
Choose Discover > APIs.
Search for the package Connect to SAP Business Technology Platform Services and select it.

choose API Navigate to Artifacts tab, where you find one artifact.
Under Actions, choose Copy.

Actions Once the artifact was copied successfully, go to Configure > APIs.
Choose the API that you created in the previous step.

API Proxy Choose Edit.

Edit Select Policies.

Policies The policy editor opens.
Choose Policy Template > Apply.

Policy Template Select the template
Cloud_Platform_Connectivityand choose Apply.
add Template Open the node Target Endpoint.

TargetEndPoint Choose
PreFlow.
PreFlow In the editor, the OAuth workflow defined by the policy is visualized as a graphical model.
Now, you need the values copied from the service key:
clientid,clientsecretandtokenurl.In the graphical model of the Policy Editor, choose the
getcredentialshape.
Graphic Model Paste the value of
clientidandclientsecretas shown in the following image.
Values In the policy editor, choose the
getoauthtokenshape.
token Paste the value of
tokenurlas shown in the following screenshot.Note: Make sure that you append
?grant_type=client_credentialsto the token URL that you pasted.
tokenURL Select Update.

tokenURL Select Save.

Save To deploy your changes, choose Click to Deploy in the message strip at the top of the screen.

Save Confirm the deployment.
You’ve now assigned a policy template to your API.
In this step, you try out the API to get product details as a response from the web shop.
Go to the Resources tab.

ResourceTab Choose Try Out.

try out Choose Execute.

Execute As result, you see the response from the
WebShopwith the product details for the given product identifier.
WebShop
You have successfully set up your SAP Integration Suite tenant, designed a simple integration flow that reads data from a remote component, and defined the integration flow endpoint as an API. Finally, you have successfully called the API to get product details as a response from the remote component.
This scenario showed you how to use SAP Integration Suite, and in particular, its Cloud Integration and API Management capabilities seamlessly integrated, end-to-end.
Resources
Discussion
Share feedback on this tutorial or join the conversation in SAP Community.