DRM Rights Service API Specifications (Version 1.0)
Fetch
fetch
Get the data permissions of eligible dp_ids found by DRM Rights Service for the data use case specified in the request body. The ids of request parameters are available to be looked up in DRM CloudSQL mysql server now and DRM UI in the future. NOTE: The fetch API should be called every time for obtaining the latest dpPermissions and a new delivery token for the data use case, previously obtained eligible dp_ids and delivery_token should not be cached on the caller's end to be reused for the multiple data generation of the same data use case.
The fetch request body contains the data use case parameters.
A DpPermission list of eligible dp_ids will be returned if there are eligible dp_ids found for the given data use case. A delivery_token will also be issued if fetchForDelivery is set to true in the request body.
No eligible dp_id is found due to invalid parameters or values in the request. A short reason and detailed error message will be provided in the response.
Unauthorized error
No eligible dp_id is found regarding the given data use case. A short reason and detailed error message will be provided in the response.
Validate
validate
Check with DRM rights service for getting the data delivery validated and approved before taking action to deliver the data. NOTE: the delivery_token must be paired with the output data generated for the delivery which this delivery_token was issued for. A delivery_token should neither be reused for delivering multiple data snapshots generated across time for the same data use case nor be used for the output data of other data use case.
The request body needs to contain the previously issued delivery_token and the required information.
The data delivery is validated and approved. The "approved" will be set to true in the response.
The data delivery is unapproved due to invalid parameters or values in the request. The "approved" will be set to false in the response and a short reason and detailed error message will be provided in the response.
The data delivery is unapproved due to a specific reason. The "approved" will be set to false in the response and a short reason and detailed error message will be provided in the response.