You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

The following diagram describes the exchange flows for registration and retrieval of documents hosted in WIPO DAS by notification to OSF

Exchange flow to register document


StepAPI RequestNotes
(1a) - OFF requests a pre-signed URL from WIPO DAS to upload a file identified by a file idPOST /das/v1/requests/files/url-uploadsNot required if OFF keeps the actual document file content in its own digital library
(1b) - OFF uploads the document file content using a pre-signed URL given in step (step 1a)File upload via PUT
(1c) - OFF requests document registration to WIPO DAS by referring to the uploaded file content by the corresponding file idPOST /das/v1/requests/registrations

Postman demo test

d.1.1.- Registration process

Exchange flow to correct filing date or parent application details in which the foreign priority document is held 

StepAPI RequestNotes
(1c) - OFF requests document registration to WIPO DAS by specifying the new document attributesPUT /das/v1/requests/registrations



The following diagram describes the exchange flows for registration and retrieval of documents hosted in WIPO DAS by notification to OSF

Figure A: Notification of document availability

Exchange flow to register document

Steps (1a) and (1b) are not required if the OFF keeps the actual document file content in its own digital library

Postman demo test

d.1.1.- Registration process

Exchange flow to correct filing date or parent application details in which the foreign priority document is held 

  • (1c) - OFF requests document registration to WIPO DAS by specifying the new document attributes (i.e. PUT /das/v1/requests/registrations) 

Exchange flow to replace document content for correction purpose 

  • (1a) - OFF requests a presigned url from WIPO DAS to upload a file identified by a file id (i.e. POST /das/v1/requests/files/url-uploads) 
  • (1b) - OFF uploads the corrected document file content using a presigned url given in step (1a)
  • (1c) - OFF requests document registration to WIPO DAS by referring to the uploaded file content by the corresponding file id (i.e. PUT /das/v1/requests/registrations)

Exchange flow to retrieve document hosted in WIPO DAS

  • (2a) - OSF sends a document retrieval request to WIPO DAS and receives a request acknowledgement id (i.e. POST /das/v1/requests/retrievals)
  • (2b) - WIPO DAS prepares the requested document for download and notifies the OSF of the document availability (i.e. Figure A) by referring to the request acknowledgement id returned in step (2a) (i.e. POST /das/v1/requests/notifications) 
Alternatively , OSF may use the check status (i.e. Figure B) to download the document content when it is reported as available by WIPO DAS (i.e. GET /das/v1/requests/retrievals) 
  • (2c) - OSF retrieves file location URL from WIPO DAS to download the document file content (i.e. POST /das/v1/requests/url-downloads). Downloads can be repeated while the requested document is not deleted from WIPO DAS
  • (2d) - OSF downloads file from WIPO DAS 
  • (2e) - Optionally OSF deletes the download files from the DAS transit zone (i.e. DELETE /das/v1/requests/files) 
If OSF does not delete the downloaded file, WIPO DAS will delete it after a pre-defined period (e.g. 1 week)

The following diagram describes the exchange flows for registration and retrieval of documents hosted in WIPO DAS and the OSF checking on regular basis statuses of retrievals requests

Figure B: OSF checking document availability

Postman demo test

d.2.1.- Succesful retrieval example



  • No labels