Tender registration consists of primary record creation and documentation uploading.
When registering tender in the database, one has provide all primary tender details (except binary documents) in payload of request.
http
POST /tenders HTTP/1.1
The produced response will contain URL of the created tender in Location header of response, and in data.id
of body.
http
HTTP/1.1 201 Created Location: /tenders/64e93250be76435397e8c992ed4214d1
All tender documentation should be uploaded with the following request - one request per document. You can see supported request types in upload
section.
http
POST /tenders/64e93250be76435397e8c992ed4214d1/documents HTTP/1.1
The response produced will have URL of the tender uploaded document in Location header of response and in data.id
of body.
http
HTTP/1.1 201 Created Location: /tenders/64e93250be76435397e8c992ed4214d1/documents/6a7d13bd8ec449e08882aeb92180d938
Example request:
Procuring Entity can change both the primary record and associated documentation.
Procuring Entity can change the Tender properties with the following request. Data to change should be in payload of the message.
http
PATCH /tenders/64e93250be76435397e8c992ed4214d1 HTTP/1.1
http
HTTP/1.1 200 OK
Procuring Entity can upload new versions of the tender documentation. You can see supported request types in upload
section.
http
PUT /tenders/64e93250be76435397e8c992ed4214d1/documents/6a7d13bd8ec449e08882aeb92180d938 HTTP/1.1
http
HTTP/1.1 200 OK
Example request:
The same as procuring-uploading-docs
.