Name: Exploring Accounts API in SAP Customer Data Cloud
Uploaded: 2018-6-28
Duration: 195 s

Share feedback

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

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div>In this video, you'll learn all about Customer Data Cloud’s Accounts APIs. They're the core of the Registration-as-a-Service (RaaS) platform, providing the basic building blocks of functionality. </div><div><br></div><div>The API gives you complete flexibility in terms of design and maintaining full control of the server-side integration. The Accounts API provides access to the user account data stored by Customer Data Cloud. The user data stored includes Customer Data Cloud's predefined fields, social graph, and site's specific custom fields.</div><div><br>The Accounts APIs are supported both for client-side (Web SDK) and server side (REST API). We encourage you to use server-side APIs whenever applicable. If you'd like to get more advanced with your RaaS CIAM solution, checkout these videos!</div></div><br></div></div>

Exploring Accounts API in SAP Customer Data Cloud

In this video, we'll be discussing the accounts API and how to use it. Because of the many number of workflows that can be created using the accounts API, both on the client side and on the server side, we won't be going into any examples in this video. However, if you do want to see some examples or get some ideas, you can always visit Developer's target.com and review the documentation there. The accounts API is accessible both from the client side as well as the server side, with server side accounts API calls having more available methods. Most of the additional server side methods are targeted toward account and user administration. Using the accounts API, you could build your own custom user workflows, similar to having done so with markup extensions, with the main difference being that using the accounts API, you would also be responsible for the user interface for those login workflows. It is also important to understand that a successful implementation with Customer Data Cloud does not necessarily require any accounts. API implementation. However, with it, an integration with CDC does become much more powerful. From the client side, the accounts API can only target the current user session, whether they're authenticated or attempting to authenticate. If you intend to develop your own customized workflows and your own custom uses, the Client Side Accounts API exposes all the methods you will need in order to do so. There are some other methods available as well, but for security reasons, the information that they provide is only a subset of the information available using the server side accounts API methods. Using the accounts API from the server side is much more powerful because of the added authentication of using the CDC secret key. You will be able to target all of your users regardless whether they are currently logged in or not, which can be very useful in administrative circumstances because all of the client side methods are also available from the server side. It is also possible to create custom workflows using the accounts API from the server side. Doing so provides the option of sending session information to the client side for client side SDKs to use. Or you could keep CDC off the client side entirely and manage the session completely on the server side. The server side Accounts API also offers other administrative methods such as account stat search, get set schema, and Get set policies by using these and all of the other available administrative methods. It is possible to build console functionality into a content or site management system that you may be using. The accounts API offers dozens of different methods that can be used both to customize user workflows, as well as administer policies and settings on the API keys being used to make the most out of the accounts API. It is strongly recommended that you peruse documentation.