...
- Method for authentication and authorization. Also need to determine if the same auth methods will be used by the Bridge and the Gateway
Bridge API
| Table of Contents |
|---|
Bridge API - Endpoints to be used by OTM Gateway
Bridge Details
- Provides information about the bridge application
- Request:
GET /bridge Response Body: JSON
Code Block { "bridge-version" : "", "supported-checksum-types" : "" # Possible values: MD5, SHA-256, SHA-512 }- Response Code: 200 (on success)
...
- Purpose: Allows the repository to retrieve restored content from the Bridge
- Request:
GET /bridge/restore/{restore-id}/{file-id} ? {checksum-type}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
...
Bridge API - Endpoints to be used by DDP
Add Account
- Purpose: Allows the DDP to inform the Bridge of a new OTM account. After this call it will be possible for the OTM endpoint to contact the Bridge.
...
- Purpose: Allows the DDP to inform the Bridge that a deposit has completed and no longer needs to be maintained in staging storage.
...
DDP API - Endpoints to be used by the Bridge
Content Ready for Deposit
...