Skip to main content
This guide introduces the REST API functionality delivered by the Digital Identity Management identity management service. Digital Identity Management provides a library of REST APIs that client applications (i.e., JavaScript UIs) execute to perform user lifecycle management functions against Digital Identity Management data entities within the cloud. Our library enables your organization’s client developers to quickly build identity services and security into your UIs, all while that data and functionality are managed, as a service, within the MarketONE data store.

​
Digital Identity Management API Features

The Digital Identity Management API library is designed for a variety of user-centric capabilities, including:
  • User provisioning and user management; for example, user onboarding, authentication, authorization
  • Service modeling; that is, mapping external account data to Digital Identity Management Account/Subscription/Feature (A/S/F) data entities
  • Service sharing; that is, by way of Digital Identity Management User-to-A/S/F, Group-to-A/S/F, and User-to-Group data associations
  • Service support; for example, retrieve and manage user information in CRM systems
  • High volume machine-to-machine data synchronization between Digital Identity Management and authorized external systems
  • Service entitlement and secure access to resources in business-to-customer contexts; for example, authenticate a user, and retrieve their service entitlements, before granting them access to a service
  • Initialize Digital Identity Management Processes to perform more complex, multiple-call operations that guide front end UIs

​
Who Is Digital Identity Management For?

Digital Identity Management is designed for both small and large-scale businesses seeking to simplify and streamline user identity management. This solution is suitable for organizations looking to implement or enhance their digital transformation strategies with minimal infrastructural changes, leveraging REST APIs for a variety of identity and user information management purposes.

​
About This Guide

This guide is one half of a broader set of programming documentation for UI developers looking to leverage Digital Identity Management’s identity management capabilities in their client applications. If you’re new to Digital Identity Management and or RESTful API, then use this guide to familiarize yourself with the basics of how REST works in Digital Identity Management. Then, when you’re ready, check out the Digital Identity Management API Process Guide for detailed information on how our patented Digital Identity Management Processes enable your applications to deliver streamlined, adaptive user journeys.

​
REST and JSON

Representational State Transfer (REST) is an architectural style built on HTTP standards, and designed around clean, lightweight exchange of data between client and server. RESTful APIs do not return any sort of markup or styling (HTML or CSS). Instead, they return serialized data that a client application consumes, parses, and displays in whatever manner that it requires. Developers can integrate Digital Identity Management REST APIs across a variety of devices and mediums – from browser-based web UIs and mobile apps, to set-top boxes and smartwatches. Digital Identity Management APIs consume and deliver resources using valid JavaScript Object Notation (JSON). JSON provides a clean, human-readable format for data while remaining lean and concise (unlike alternatives such as XML, which can be exceptionally verbose, more difficult to consume, and require more bandwidth per request to exchange data). Because of JSON’s widespread adoption for RESTful APIs, developers often have access to high-quality and high-performance libraries to assist in the serialization and deserialization of data in JSON format across a wide variety of languages, if the library used for web requests does not natively support JSON already. The implementations using Digital Identity Management APIs are compliant with HTTP specifications, and clients need produce the appropriate headers with each request, namely the Content-type header that indicates the media type for requests containing serialized data. The value provided with the header must be application/json (the standard media type for data serialized in JSON format), except in cases where a protocol dictates otherwise. Clients must also produce valid JSON on every request. Digital Identity Management returns errors when required headers are missing, or when the data provided is not in a valid JSON format.

​
Building Your Applications With REST API and API-Based Processes

Out of the box, Digital Identity Management provides a library of API endpoints that can be grouped into two major types:
  • An extensive set of “one shot” API that allows you (or your end users) to perform basic CRUD operations (Create/Read/Update/Delete) on Digital Identity Management data resources. For example, once a user signs in to a service, your application will probably call the GET /user API endpoint to retrieve their data and give them a personalized view of the application.
  • A library of process-specific API endpoints that initializes, continues, and completes Digital Identity Management Processes. A Process is flow of linked API requests that fulfills standard user lifecycle use cases, that enables UI developers to easily build and deliver identity management capabilities (onboarding, authentication, password management, social login, etc.) to their end users.
In other words, Digital Identity Management Processes are distinct from, but work in concert with, standard REST API calls. As a UI Developer, you’ll need to familiarize yourself with the concepts of REST (Representational State Transfer), the Digital Identity Management data model, and how each Digital Identity Management Process works. You’ll then want to build your client application(s) with our multi-step Processes, as well as our standard single-call REST APIs, as needed and according to your desired use cases.