Explaining APIs and Webhooks

Objectives
After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Articulate the key considerations and use cases of SAP WZ APIs and Webhooks

APIs and Webhook Implementation

Application Programmable Interfaces (APIs) are primarily used by other SAP or third party solutions to integrate with SAP Build Work Zone, to either query data-based on scope, or create new content. On the other hand, webhook subscriptions are used to register for notifications of certain updates or activities within SAP Build Work Zone.

Note
The aspects covered in this unit are specifically referring to the Digital Workplace Service (DWS) component of the SAP Build Work Zone solution architecture. This impacts all related aspects, such as, required API endpoints, API authentication, and more.

In the context of integrating with SAP and third party solutions, APIs and webhook (subscriptions) play an important role. First, the following items related to the technical implementation on SAP Build Work Zone need to be well understood:

  • APIs are available as OData or REST services.
  • User authorization and authentication can be done using OAuth1.0a or 2.0 workflow, or SAML assertions from a trusted identity provider.
  • APIs also support single-use tokens for granting immediate, short-term access to single pages.
  • Webhooks are used to register callback end points for supported events. When such an event occurs, it notifies registered subscribers.

A typical integration flow using APIs could look like this:

A typical integration using webhook subscriptions could look like this:

Integration Use Cases Leveraging APIs and Webhooks

After looking at the technical implementation and setup for API or webhook-based integration scenarios, this lesson will highlight some example use cases. As seen from the broad range of topics though, the possibilities are extremely broad.

Save progress to your learning plan by logging in or creating an account