Name: Integrating API with Server Applications on SAP Customer Data Platform
Uploaded: 2024-2-15
Duration: 359 s
Description: In this video on SAP Customer Data Platform API Integration via Server Applications, we will configure a server application and send API calls to ingest customer data through a server application event.

Share feedback

<p>Planned maintenance of Practice Systems</p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div>In this video on SAP Customer Data Platform API Integration via Server Applications, we will configure a server application and send API calls to ingest customer data through a server application event.  </div></div>

Integrating API with Server Applications on SAP Customer Data Platform

In this video on SAP Customer Data Platform API Integration  via Server Applications,   we will configure a server application  and send API calls to ingest customer data  through a server application event.   Let’s start by creating a server application  from the application library.    In the SAP Customer Data Platform,  go to Sources under Connect   and choose the Connect Application button.   It opens the Application Library,  which shows the out-of-the-box integrations  available for SAP CDP.   Here, you can see Server Application integration on the Custom Applications tab.   It supports both inbound data ingestion via events and outbound data activation via actions.   Still, no events or actions are defined  on the connector out of the box,  and we need to define them  on the server application manually.   Choose Create to create a server application.   Enter a Name   and turn on Activated.   Then, choose Create.   Choose the three-dot action dropdown menu on the source application screen  and select Edit.   On the Edit Application popup, choose the Application Key tab,   copy the User Key and Secret Key fields,  and make a note of the values.   We’ll use them to send the API calls.   When creating a server application,  an asymmetric RSA key pair  is assigned to the application.   If you want to sign the API calls  using JWT tokens,  you can choose the Generate button  to generate the private key.   You need to copy and make a note  of the private key because it’s only available  once inside the pop-up.   Otherwise, you’ll have to generate a new key pair.  We will use the user key  and secret to call the CDP API.   On the Destination Purposes tab,  choose the processing purposes  for the server application to access customer data.  Choose Save to close the popup.   Back on the source application screen,  choose Create New Event to define the event, through which to ingest the customer data into the CDP.   On the Settings tab of the New Event screen,  enter a Name,   choose a Data Type,   assign Granted Processing Purposes,   and choose Next.   On the Model tab,  choose + Create Node  to add the event schema fields.   Let’s add the email,   firstname   and lastname fields,   and choose Next.   On the Matching Rules Mapping tab,  drag the E-Mail field in the event schema  on the left side  and drop it into the primaryEmail field  in the profile schema on the right side.   Choose Next.   On the Schema Mapping tab,  map the First Name and Last Name fields,   and choose Next.   On the Listener tab, copy the URL.   This URL is the CDP API endpoint,  to which we’ll send the event data ingestion API call.  Choose Done  to go back to the source application screen.   The server application and event  are ready for API calls.  Open the RESTful API client tool   and create a POST request  for the endpoint / URL  we copied on the create event screen.   Add the userKey and secret request parameters  and enter the values we copied  from the server application.  Please make sure  to URL encode the secret parameter value,  otherwise the API call might fail  with a 403 Forbidden error  if the secret contains  any non-alphanumeric characters like “+” or “$”.  Next build a JSON request body,   making sure the JSON fields  exactly match the event schema fields.   Now send the API call.   We’ll get a 202 response status code  and an empty response body,  meaning the API call is successful.   Now you can go to Search  under Customers   to see the new customer profiles ingested  through the server application event.   This completes the API integration  with server applications demo.   Thank you for watching.