Iron Mountain InSight Core Data Vault (CDV) APIs

Owned by InSight System
Jan 27, 2020
47 min read

Contents

Introduction

The Core Data Vault (CDV) APIs are used to define and query metadata fields as well as to upload, edit and export documents.   

The high level architecture diagram below shows the REST CDV APIs.  This API documentation provides instructions for an IRM partner or customer to access these APIs.

Access to an environment for testing the APIs requires approval to get the necessary security tokens.   Access by partners is only given to specific data when requested and agreed upon by an InSight customer.



The services below marked with * are  for Q1 2020 (not yet released).

Document & Attribute Values APIs

Service Name

API Contracts

Note

Permissions Required

Service Name

API Contracts

Note

Permissions Required

Create Asset Document & Attribute Values

POST /companies/{companyId}/documents

Request Body: AssetDocument

{ "documentTypeId":"00000000-0000-0000-0000-000000000001", "fileName":"test.pdf", "mlPipeline": "ml1", "barcode": "20011234567890", "attributeValues":[ { "name": "departmentId", "value": "2222" }, { "name": "divisionId", "value": "1111" }, { "name": "majorDescription", "value": "test 3" }, { "name": "count", "value": "20" } ] } Or remote storage for the document: { "documentTypeId":"00000000-0000-0000-0000-000000000001", "fileName":"test.pdf", "mlPipeline": "ml1", "barcode": "20011234567890", "remoteStorage":true, "connectorConfigId":"ca1885e4-4207-474e-8cdf-3eabd70cafe2", "externalDocumentId":"https://s3.amazonaws.com/bill-test-dit2/Insight/600163.pdf", "attributeValues":[ { "name": "departmentId", "value": "2222" }, { "name": "divisionId", "value": "1111" }, { "name": "majorDescription", "value": "test 3" }, { "name": "count", "value": "20" } ] }

Response: AssetDocument

{ "createdDate": "2018-07-30T17:49:10.042+00:00", "createdUserId": "gateway", "companyId": 2001, "documentGUID": "c29d43fe-06a4-400e-9166-eb15f865d3b5", "documentTypeId": "00000000-0000-0000-0000-000000000001", "size": 0, "state": "METADATA_UPLOADED", "fileName": "test.pdf", "fileStorageId": "00000000-0000-0000-0000-000000000001", "deleted": false, "lastAccessDate": "2018-07-30T17:49:10.042+00:00", "lastAccessUserId": "gateway", "mlPipeline": "ml1", "pageCount": 0, "barcode": "20011122334455", "attributeValues": [ { "attributeValueId": "39056acf-0810-4b7a-bb29-039aee57efbd", "type": "long", "value": "1111", "name": "departmentId" }, { "attributeValueId": "83d0d652-670a-4d92-afcf-cdc3d098b57b", "type": "long", "value": "1111", "name": "divisionId" }, { "attributeValueId": "7c6b05de-2258-4ce9-84e1-bd8f89bccab7", "type": "String", "value": "test 6", "name": "majorDescription" }, { "attributeValueId": "aa95ca28-8a2f-4b99-bd6d-23d32fd4aefb", "type": "long", "value": "1", "name": "count" } ], "remoteStorage": false, "imageURL": "https://storage.cloud.google.com/rmaas-us-dit1/company/2001/...", "imageDownloadURL": "https://storage.googleapis.com/rmaas-us-dit1/company/2001/...", "imageUploadURL": "https://storage.googleapis.com/rmaas-us-dit1/company/2001/...", "imageContentType": "application/pdf" }





  • Basic data fields documentTypeId and fileName are required. See below for the requirement of fileName.

  • Basic data fields mlPipeline, barcode, facility are optional.

  • name and value are required for each attributeValue.

  • Available documentTypeId is defined in rmaas_document_type table and attribute names are defined in rmaas_attribute table.

  • If the value is invalid for the attribute type defined for the attribute name, the API returns an exception. For a Date type, the value must be in the format of defined patterns.

  • fileName and size will be updated once the image file is uploaded via the Upload/Update an Image API.

  • The server can accept a documentGUID generated by the client

  • To enable the remote storage, please specify remoteStorage, connectorConfigId and externalDocumentId (as Global URL)

  • retentionCalculationStatus=null







  • An authenticated user with the following permissions:

    • assets.use

Update Asset Document & Attribute Values *

PUT /companies/{companyId}/documents/{documentGUID}

Request Body: AssetDocument

  1. Update basic data fields and attribute values in a Document

{ "state": "METADATA_UPLOADED", "fileName": "test.pdf", "mlPipeline": "ml1", "facility": "test", "barcode": "20011122334455", "attributeValues":[ { "name": "departmentId", "value": "2222" }, { "name": "divisionId", "value": "1111" }, { "name": "majorDescription", "value": "updated description" }, { "name": "count", "value": "1" } ] }

  1. Update basic fields only



Response: AssetDocument



  • Basic data fields state, fileName are required. fileName can be either the old name or a new one, but it must be non-blank. See below for the requirement of fileName.

  • Basic data fields mlPipeline, barcode, facility are optional.

  • name and value are required for each attributeValue.

  • Available attribute names are defined in rmaas_attribute table.

  • If the value is invalid for the attribute type defined for the attribute name, the API returns an exception. For a Date type, the value must be in the format of defined patterns.

  • The image file will be moved to the new name fileName. If the file with fileName is present in GCS, it will be override.

  • The name of an attributeValue should be already defined in the document type linked to the document.

  • If the name of an attributeValue is the trigger attribute name of the document type's retention rule, the document's retentionCalculationStatus is reset to RECALCULATE so that the backend calculation task to start the calculation.



  • An authenticated user with the following permissions:

    • assets.use

Update a document Attribute Values Only *

PUT /companies/{companyId}/documents/{documentGUID}/attributes

Request Body: List<AssetAttributeValue>

Response: List<AssetAttributeValue>



  • This API updates the values for the attributes already defined in the document type with the documentTypeId.

  • documentTypeId, name and value are required.

  • documentTypeId should be the same for all attribute values, and it must be the same one linked to the document.

  • Available documentTypeId is defined in rmaas_document_type table and attribute names are defined in rmaas_attribute table. For each company, a document type "DEFAULT" is pre-created.

  • If the value is invalid for the attribute type defined for the attribute name, the API returns an exception. For a Date type, the value must be in the format of defined patterns.

  • If the name of an attributeValue is the trigger attribute name of the document type's retention rule, the document's retentionCalculationStatus is reset to RECALCULATE so that the backend calculation task to start the calculation.





  • An authenticated user with the following permissions:

    • assets.use

Update Asset Document State Only

PUT /companies/{companyId}/documents/{documentGUID}/fields/state/{state}

Request Examples:

companies/2001/documents/c29d43fe-06a4-400e-9166-eb15f865d3b5/fields/state/DOCUMENT_UPLOADED

companies/2001/documents/c29d43fe-06a4-400e-9166-eb15f865d3b5/fields/state/METADATA_UPLOADED

Response: AssetDocument



This API updates the document state only. The new state is passed in the URL. Available states are

  • METADATA_UPLOADED

  • DOCUMENT_UPLOADED

  • PROCESSED

  • INDEXED

  • REPROCESS

  • An authenticated user with the following permissions:

    • assets.use

Get Asset Document *

GET /companies/{companyId}/documents/{documentGUID}

Response: AssetDocument



  • The following data fields are also returned as attribute values if retention destruction eilibility date is calculated.

    • DestructionEligibilityDate

    • RetentionTriggerDate

    • Jurisdiction

    • RetentionRecordClass

    • RetentionPeriod

    • RetentionPeriodUnits

    • RetentionTriggerField



  • An authenticated user with the following permissions:

    • assets.view

Delete Asset Document

DELETE /companies/{companyId}/documents/{documentGUID}?

Query Parameter: permanent is optional (true or false), requestId is optional (any string). if permanent=true, the document and its related data will be deleted permanently immediately.

Response: 1

document and attribute values are deleted

  • An authenticated user with the following permissions:

    • assets.manage

Restore/Undo-Delete Asset Document

PATCH /companies/{companyId}/documents/{documentGUID}

Response: AssetDocument



  • An authenticated user with the following permissions:

    • assets.manage

Query All documents *

GET /companies/{companyId}/documents

Query Parameter: deletedOnly is optional. Only soft-deleted documents returned if deletedOnly=true

Support Query Pagination, Sorting and Filtering

  • If companyId=0, then apply to all companies

  • The following data fields are also returned as attribute values if retention destruction eilibility date is calculated.

    • DestructionEligibilityDate

    • RetentionTriggerDate

    • Jurisdiction

    • RetentionRecordClass

    • RetentionPeriod

    • RetentionPeriodUnits

    • RetentionTriggerField

  • An authenticated user with the following permissions:

    • assets.view

Get attribute value histories for a Document

GET /companies/{companyId}/documents/{documentGUID}/histories

Response: List<AssetAttributeValueHist>







Get attribute value histories for a company

GET /companies/{companyId}/documents/histories

Response: List<AssetAttributeValueHist>







Download the media File for a document

GET /companies/{companyId}/documents/{documentGUID}/media

Response: A file content



  • An authenticated user with the following permissions:

    • assets.view

Update document metadata in Batch mode

PUT companies/{companyId}/documents?state=<30 or 40>

Request: See document_batch_metadata_esMetaData.json

Response:





Internal Use only



Trigger A Destruction Process for Documents, their attribute values and image/support files

DELETE: /companies/{companyId}/documents?requestId=<request id>

Request Body: List<String> documentGUIDs, List<String> emailTos.



Response: 1, process is started successfully; 0 otherwise.

  • requestId can be any free text currently. The validation rule is TBD.

  • documentGUIDs is required and should at least include one documentGUID.

  • emailTos is optional. If it includes an email address, the destruction report will be sent to it as an attachment.

  • Documents, their attribute values and image/support files will be deleted immediately.

  • An authenticated user with the following permissions:

  • assets.manage

Download the Destruction Report for a request

GET: /companies/{companyId}/documents/destructionReport

Request Param: emailTos (optional), requestId (optional), fromDate (optional) - ISO date format, toDate (optional) - ISO date format

Response: a csv file

  • requestId can be any free text currently. The validation rule is TBD.

  • 0 or multiple emailTos can be sent in the request, for example:

    emailTos=email1,email2,email3



Calculate the Retention Destruction Eligibility Date for a Document *

Internal Use Only

PATCH: /companies/{companyId}/documents/{documentGUID}/retention/calculation

Response: AssetDocument with retention attribute values

  • Calculation is started for a document with retentionCalculationStatus=RECALCULATE or it is null (null pointer, not "NULL" status).

  • An authenticated user with the following permissions:

  • assets.manage

Trigger a Task to Calculate the Retention Destruction Eligibility Date for all Documents of a Company *

Internal Use Only

PATCH: /companies/{companyId}/documents/retention/calculation

Response: 1, the task is started successfully; 0 otherwise.



  • An authenticated user with the following permissions:

    • assets.manage

Trigger a Task to Calculate the Retention Destruction Eligibility Date for all Documents of a Document Type *

Internal Use Only

PATCH: /companies/{companyId}/documentTypes/{docTypeId}/documents/retention/calculation

Response: 1, the task is started successfully; 0 otherwise.

  • docTypeId is a valid document type id

  • An authenticated user with the following permissions:

    • assets.manage

Trigger a Task to Reset the Retention Calculation Status for all Documents of a Company *

PATCH: /companies/{companyId}/documents/retention/status

Response: 1, the task is started successfully; 0 otherwise.



  • An authenticated user with the following permissions:

  • assets.manage

Trigger a Task to Reset the Retention Calculation Status for all Documents of a Document Type *

PATCH: /companies/{companyId}/documentTypes/{docTypeId}/documents/retention/status

Response: 1, the task is started successfully; 0 otherwise.

  • docTypeId is a valid document type id

  • An authenticated user with the following permissions:

  • assets.manage



Example image URLs:


Document State Mappings

State Text in Request/Response

State Value

State Text in Request/Response

State Value

METADATA_UPLOADED

10

DOCUMENT_UPLOADED

20

PROCESSED

30

INDEXED

40

REPROCESS

50

Retention Calculation Status 

Retention Calculation Status



Retention Calculation Status



RECALCULATE

ready for calculation

CALCULATING

in the process of calculation

DONE

calculation is finished with RetentionErrorCode (see below table).

Retention Error Code

Retention error code



Retention error code



SUCCESS

Retention eligibility date is calculated successfully.

RETENTION_PERIOD_MISSING

There is no retention period.

RETENTION_PERIOD_UNIT_MISSING

There is no retention period unit. Usually it is years, months, days for PCS retention rules.

RETENTION_PERIOD_UNIT_INVALID

The retention period unit is not either of years, months, days.

DOCUMENT_TYPE_MISSING

There is no document type id for the document.

RULE_MISSING

There is no retention rule for the document type of the document.

RETENTION_TRIGGER_ATTRIBUTE_MISSING

There is no retention trigger attribute id (name) for the retention rule of the document type of the document.

RETENTION_TRIGGER_DATE_MISSING

There is no attribute value for the document for the retention trigger attribute.

RETENTION_TRIGGER_DATE_INVALID_TYPE

The attribute value is not a "Date" type.

RETENTION_TRIGGER_DATE_INVALID

The attribute value (string presentation) cannot be parsed as a Date.

NO_RETENTION_TYPE

The company is neither CUSTOMER nor PCS retention type.

EXCEPTION

Runtime exception(s) occur during the calculation.

Document Images / Files APIs

ES stands for ElasticSearch

Service Name

API Contracts

Note

Permissions Required

Service Name

API Contracts

Note

Permissions Required

Update ES metadata only

PUT /companies/{companyId}/documents/{documentGUID}/es

Request Body: text



  • An authenticated user with the following permissions:

    • assets.use

Get ES metadata

GET /companies/{companyId}/documents/{documentGUID}/es

Response : text



  • An authenticated user with the following permissions:

    • assets.view

Upload/Update an Image

POST /companies/{companyId}/documents/{documentGUID}/image

Request Body: multipart/form-data (file & fileName)

  • file and fileName (or filename) are required. The field fileName (or filename) is the name of the uploaded file in the GCS folder. It can be different from the name of the file. See below for the requirements of fileName and filename.

  • An authenticated user with the following permissions:

    • assets.use

Upload/Update an Image by resource

PUT /companies/{companyId}/documents/{documentGUID}/image

Request Body: ResourceUploadInfo



  • connectorType is required. It must be one of the connector types listed on the Connector Config APIs page.

  • resourceLocation is required.

  • An authenticated user with the following permissions:

    • assets.use

Download an Image

GET /companies/{companyId}/documents/{documentGUID}/image

Response: URL



  • An authenticated user with the following permissions:

    • assets.view

Upload/Update a Support File

POST /companies/{companyId}/documents/{documentGUID}/files

Request Body: multipart/form-data (file & fileName)

  • file and fileName (or filename) are required. The field fileName (or filename) is the name of the uploaded file in the GCS folder. It can be different from the name of the file. See below for the requirements of fileName and filename.

  • An authenticated user with the following permissions:

    • assets.use

Download a Support File

GET /companies/{companyId}/documents/{documentGUID}/files/{fileName}

Response: URL



  • An authenticated user with the following permissions:

    • assets.view

Delete a Support File

DELETE /companies/{companyId}/documents/{documentGUID}/files/{fileName}



  • An authenticated user with the following permissions:

    • assets.manage

Delete all of Support Files

DELETE /companies/{companyId}/documents/{documentGUID}/files



  • An authenticated user with the following permissions:

    • assets.manage

List all of Support Files

GET /companies/{companyId}/documents/{documentGUID}/files
Response: a list of support file names.



  • An authenticated user with the following permissions:

    • assets.view

Requirements for a file name

fileName and filename must be less than 950 characters. They can not contain the following characters. 

 

Attributes / Metadata Fields APIs

Service Name

API Contracts

Note

Permissions Required

Service Name

API Contracts

Note

Permissions Required

Get metadata fields Data Type Mapping

GET /companies/{companyId}/attributes/dataTypes

Response : AssetMetadataTypeListResponse







Get Asset Attribute

GET /companies/{companyId}/attributes/{attributeId}

Request Body: None

Response : AssetAttribute





An authenticated user with the following permissions:

  • classification_doc_types.manage

OR

  • classification_doc_types.view

Query Asset Attributes

GET /companies/{companyId}/attributes

Support Query Pagination, Sorting and Filtering



Response: List<AssetAttribute>











Create Attribute

POST /companies/{companyId}/attributes

Request Body: List<AssetAttribute>

Response: AssetAttribute



  • name, type, displayable, mandatory, searchable, and encrypted are required for each attribute. validationRegex is optional.

  • For each attribute, type must be one of "String", "Date", "int", "long", and "boolean". For "String" type, "validationRegex" must follow Java regex Pattern definitions. For "Date" type, "validationRegex" must follow pattern definitions on Java SimpleDateFormat.

An authenticated user with the following permissions:

  • classification_doc_types.manage

Update Asset Attribute

PUT /companies/{companyId}/attributes/{attributeId}

Request Body: AssetAttribute

Response : AssetAttribute





An authenticated user with the following permissions:

  • classification_doc_types.manage

Update Asset Attributes

PUT /companies/{companyId}/attributes

Request Body: List<AssetAttribute>

Response: AssetAttributeListResponse





An authenticated user with the following permissions:

  • classification_doc_types.manage

Delete Asset Attribute

DELETE /companies/{companyId}/attributes/{attributeId}

Request Body: None

Response : ServiceResponse<Integer>





An authenticated user with the following permissions:

  • classification_doc_types.manage

Delete Asset Attributes

DELETE /companies/{companyId}/attributes

Request Body: List<String> - a list of attributeId's

Response : ServiceResponse<Integer>





An authenticated user with the following permissions:

  • classification_doc_types.manage

Assign/Unassign/Override an attribute Id to document type ids *

PUT /companies/{companyId}/attributes/{attributeId}/documentTypes?action=<ASSIGN,UNASSIGN or OVERRIDE>

Request Body: documentTypeIds

Response: AssetAttribute

  • is not empty to assign/unassign to an attribute. But it can be empty array/list to override document type ids, in this case, the current document type ids will be totally cleared. Each item must be a valid company document type id.

  • A RmaasPreconditionException is returned if action=UNASSIGN and the attribute is the retention trigger attribute of the document type.

An authenticated user with the following permissions:

  • classification_doc_types.manage

Assign/Unassign/Override attribute Ids to document type ids *

PUT /companies/{companyId}/attributes/documentTypes?action=<ASSIGN,UNASSIGN or OVERRIDE>

Request Body: attributeIds and documentTypeIds

Response:  List<AssetAttribute>

  • must be non empty and each item has to be valid attribute id of the company.

  • is not empty to assign/unassign to attributes. But it can be empty array/list to override document type ids, in this case, the current document type ids will be totally cleared. Each item must be a valid company document type id.

  • A RmaasPreconditionException is returned if action=UNASSIGN and one of attributes is the retention trigger attribute of either document type.

An authenticated user with the following permissions:

  • classification_doc_types.manage

Supported attribute data types

Attribute Type

Attribute Value

Attribute Type

Attribute Value

int

A string represents an integer, for example, "123"

long

A string represents a big integer, for example "1298381"

Date

A string represents a date or date and time in the following format patterns which are defined in Java 8 SimpleDateFormat. 



String

A plain text string

boolean

A string of "true" or "false"

double

A string represents a double, for example "1.0", or "1"

Coordinates

A string represents a coordinates point in format of "Numeric, Numeric[, Numeric]", for example "40.112312, -71.192291"



Document Type APIs

Service Name

API Contracts

Note

Permissions Required

Service Name

API Contracts

Note

Permissions Required

Create a Document Type

POST /companies/{companyId}/documentTypes

Request Body: AssetDocumentType

Response: AssetDocumentType



  • companyId=0 for all IRM defined document types

  • name and description are required. pcsDocumentTypeId is set to null if it is not present in the request body; otherwise, it is set to the value in the request (either null, blank, or a string). minConfidence is set to default value 0.85 if it is not present or it is 0.0, -0.0, null; the API returns a 400 error message if it is negative (<0.0) or > 1.0; otherwise, it is set to the value.

  • attributes are created independently.

  • An authenticated user with the following permissions:

    • classification_doc_types.manage

ASSIGN/UNASSIGN/OVERRIDE Attributes for a Document Type *

PUT /companies/{companyId}/documentTypes/{docTypeId}/attributes

Query Parameter: action=ASSIGN/UNASSIGN/OVERRIDE, default is OVERRIDE

Request: attributeIds



Response: AssetDocumentType with updated attributes



  • A RmaasPreconditionException is returned if action=UNASSIGN and one attribute is the retention trigger attribute of the document type.

  • An authenticated user with the following permissions:

    • classification_doc_types.manage

ASSIGN/UNASSIGN/OVERRIDE Attributes for Document Types *

PUT /companies/{companyId}/documentTypes/attributes

Query Parameter: action=ASSIGN/UNASSIGN/OVERRIDE, default is OVERRIDE

Request: attributeIds and documentTypeIds



Response: List<AssetDocumentType> with updated attributes

  • A RmaasPreconditionException is returned if action=UNASSIGN and one attribute is the retention trigger attribute of one document type.

  • An authenticated user with the following permissions:

  • classification_doc_types.manage

Query Document Types & Attributes by a company

GET /companies/{companyId}/documentTypes

Support Query Pagination, Sorting and Filtering

Response: List<AssetDocumentType>





  • An authenticated user with the following permissions:

    • classification_doc_types.view

Update a Document Type

PUT /companies/{companyId}/documentTypes/{docTypeId}

Request Body: AssetDocumentType without attributes



Response: AssetDocumentType without attributes



  • name and description are required. It can be the current value or the new one. minConfidence is set to default value 0.85 if it is not present or it is 0.0; the API returns a 400 error message if it is negative (<0.0) or >1.0; otherwise, it is set to the value.

  • An authenticated user with the following permissions:

    • classification_doc_types.manage

Update PCS Document Type Id *

PUT /companies/{companyId}/documentTypes/{docTypeId}/pcsDocumentTypeId/{pcsDocTypeId}

Response: AssetDocumentType without Retention Rules

  • pcsDocTypeId is a valid PCS document type id in the rmaas_retention_rule table for the company. If it is a string "null" or "NULL", the service unlinks a PCS document type for the given document type.

  • If a document type is already associated with a PCS document type, calling this API with another PCS document type id will return a RmaasPreconditionException.

  • The jurisdiction of the retention rules of the PCS document type must match company's jurisdiction.

  • After linking a PCS document type id to a document type, a Policy Manager should start a task to reset the retention calculation status for all impacted documents.

  • An authenticated user with the following permissions:

    • classification_doc_types.manage

Update Retention Trigger Attribute for a Retention Rule of a Document Type *

PUT /companies/{companyId}/documentTypes/{docTypeId}/rules/retention/{ruleId}/attribute/{attributeId}

Response: AssetDocumentType

  • attributeId is a valid attribute id of the company. This API assigns the attribute to the document type if it is not done so yet. If it is a string "null" or "NULL", the service removes it from the retention rule.

  • After linking a PCS document type id to a document type, a Policy Manager should start a task to reset the retention calculation status for all impacted documents.

  • An authenticated user with the following permissions:

    • classification_doc_types.manage

Update Retention Trigger Attribute for all Retention Rules of a Document Type *

PUT /companies/{companyId}/documentTypes/{docTypeId}/rules/retention/attribute/{attributeId}

Response: AssetDocumentType

  • attributeId is a valid attribute id of the company.This API assigns the attribute to the document type if it is not done so yet. If it is a string "null" or "NULL", the service removes it from the retention rule.

  • After linking a PCS document type id to a document type, a Policy Manager should start a task to reset the retention calculation status for all impacted documents.

  • An authenticated user with the following permissions:

    • classification_doc_types.manage

Get a Document Type *

GET /companies/{companyId}/documentTypes/{docTypeId}

Response: AssetDocumentType





  •  If the document type is associated with a PCS document type id, governanceRules is returned.

  • An authenticated user with the following permissions:

    • classification_doc_types.view

Get a list of Document Types by ids

PUT /companies/{companyId}/documentTypes

Query Parameters: details - include attributes in the response or not, default is true

Request Body: documentTypeIds

Response: List<DocumentType>







  • An authenticated user with the following permissions:

  • classification_doc_types.view

Delete a Document Type

DELETE /companies/{companyId}/documentTypes/{docTypeId}

Response: 1

Delete the document type in the spanner rmaas_document_type table if no documents is linked to this document type.

  • An authenticated user with the following permissions:

    • classification_doc_types.manage



Retention Status 

Each document type has a retention status indicating the availability of the retention rules and their retention information. If a company is NONE retention type, all document types of the company should have retentionStatus=NONE. 

Retention status



Retention status



NONE

The document type should not have a retention rule.

REQUESTED

PCS document type is requested, but there are no retention rules are created on the PCS yet.

(TBD for a document type with CUSTOMER retention type)

RETENTION_PERIOD_MISSING 

Retention rules are available, but retention period is missing

RETENTION_TRIGGER_ATTRIBUTE_MISSING 

The retention trigger attribute id(name) is not assigned yet.

RETENTION_PERIOD_TRIGGER_ATTRIBUTE_MISSING 

Neither retention period nor trigger attribute is available.

READY 

Retention rule includes retention period and trigger attribute. And it is ready for calculating the destruction eligibility date.

 

URL Structure 

https://cdvapi.<environment name>.com

Using a REST Client

  • Use a REST client such as the Google Rest Client 

  • You will need to get an authorization token from the InSight Team

  • Include the token in the header when calling the service.  See example below:





© 2020 Iron Mountain Incorporated. All Rights Reserved.