The Postman collection was structured in a way to make it easier the understanding and follow up of all the steps that are involved in the registration of a new priority document:
This process is to update the information of a previously existing "registration". In the following example, a previously existing registration, which had its attached file deleted, is updated with a new updated file
| Step | Action type | Postman request name | Notes |
|---|---|---|---|
| 1 | Generation of the authorization token | ||
| 2 | Retrieval of the file-id and pre-signed URL for the upload of a big sized document file | b.1.3.2.- obtain fileId and a presigned URL to upload a big size document file (POST) | |
| 2.1 | Retrieval of updated pre-signed URL for the already existing file-id | b.1.3.2.1.- obtain a NEW presigned URL related to an existing fileId to upload a big size document (fileId needs to be provided) | Optional step, only needed when the file upload gets delayed (so the previous URL is no longer valid). An updated URL is generated using the previously retrieved file-id |
| 3 | Upload of the file | PDF or ST.26 zip file | |
| 4 | Update to the registration | b.1.3.5.- Update of the registration | the registration should have been done earlier via the d.1.1 process, if not, this request will fail. |