Procuring Entity Operations¶
Registration of the Tender¶
Tender registration consist of primary record creation and documentation uploading.
Creating primary Tender record¶
When registering tender in the database, one has provide all primary tender details (except binary documents) in payload of request.
POST /tenders HTTP/1.1
The response produced will have URL of the tender created in Location header of resoponse, and in data.id of body.
HTTP/1.1 201 Created Location: /tenders/64e93250be76435397e8c992ed4214d1
All tender documentation should be uploaded following requests one request per document.
POST /tenders/64e93250be76435397e8c992ed4214d1/documents HTTP/1.1
The response produced will have URL of the tender document uploaded in Location header of resoponse, and in data.id of body.
HTTP/1.1 201 Created Location: /tenders/64e93250be76435397e8c992ed4214d1/documents/6a7d13bd8ec449e08882aeb92180d938
Changing the Tender¶
Procuring Entity can change both the primary record and associated documentation.
Changing primary Tender Record¶
Procuring Entity can change the Tender properties with following request. Data to change should be in payload of the message.
PATCH /tenders/64e93250be76435397e8c992ed4214d1 HTTP/1.1
HTTP/1.1 200 OK
Changing existing documents¶
Procuring Entity can upload new versions of the tender documentation.
PUT /tenders/64e93250be76435397e8c992ed4214d1/documents/6a7d13bd8ec449e08882aeb92180d938 HTTP/1.1
HTTP/1.1 200 OK
Uploading additional documents¶
The same as Uploading documentation