Page History

...

• Purpose: Allows the repository to retrieve restored content from the Bridge
• Request: GET /bridge/restore/{restore-id}/{filegroup-id}/{file-id} ? {checksum-type}
  • filegroup-id: The identifier of the filegroup for the restored file
  • file-id: The identifier of the restored file to retrieve
  • checksum-type: (Optional) Defines the type of checksum to be included in the response ETag header. Can be one of: MD5, SHA-256, SHA-512. Default is MD5.

• Response: Restored file content stream

• Response Codes:
  • 200 (on success)
  • 404 (if the file is not part of the restore or the restored content has expired)
• Response Headers: ETag

Get Audit

...

Log

• Purpose: Retrieves an audit history report. The report will list audit events associated with a single file or set of files in a filegroup.
• Request: GET /bridge/audit/{filegroup-id}/{file-id}
  • filegroup-id: The identifier of the filegroup for which an audit report is requested
  • file-id: (Optional) The identifier of the file for which an audit report is requested. If this is not provided the audit report is requested based on the filegroup-id.
• Response Codes:
  • 200 (on success)
  • 404 (if there is no audit information for the provided ID)

• Response Body: JSON 

  Code Block
  { "filefilegroup-1-id" : [ { "auditfile-event-1",id" : [ { "audit-event-2 "date" : "", }, } "type" : "", "event" : "" }, # Additional events for this file listed here ], # Additional files listed here } ] }

  
  

• Notes:
  • It may be desirable to provide paged results for large result sets
  • Types and fields of expected history events are to be listed in an appendix
  Notes:
  • Given that the primary unit of preservation is the filegroup, should this call be limited to requesting history about a filegroup?

Bridge API - Endpoints to be used by DDP

...