API Communication Flow

The following diagram illustrates how a customer application communicates with the DRM API Server to protect or unprotect files.

DRM API Server Sequence Diagram Customer Application DRM API Server 1. Authentication request to API Server 2. On successful authentication, Application recieves Access Token and Refresh Token in response 3. Upload file and passes Access Token in header 4. Application receives storage id against which the uploaded file is stored on DRM API Server 5. Calls protect/unprotect on file stored against recieved storage id and passes Access Token in header 6. DRM API server protects file with the encryption key 7. File is protected/unprotected and stored against new storage id 8. Application receives the new storage id of protected/unprotected file