.. index:: Tender
The set of possible configuration values:
You can look for more details in :ref:`config` section.
Let's provide the data attribute in the submitted body :
.. http:example:: http/tender-post-attempt-json-data.http :code:
Success! Now we can see that new object was created. Response code is 201 and Location response header reports the location of the created object. The body of response reveals the information about the created tender: its internal id (that matches the Location segment), its official tenderID and dateModified datestamp stating the moment in time when tender was last modified. Note that tender is created with draft status.
The peculiarity of the Open UA procedure is that procurementMethodType was changed from belowThreshold to aboveThresholdUA.
Also there is no opportunity to set up enquiryPeriod, it will be assigned automatically.
Let's access the URL of the created object (the Location header of the response):
.. http:example:: http/blank-tender-view.http :code:
We can see the same response we got after creating tender.
Let's see what listing of tenders reveals us:
.. http:example:: http/tender-listing-no-auth.http :code:
We don't see internal id of tender, because tender appears in the listing from active.tendering status.
Tender can contain several different lots. We can add lot using the following way:
.. http:example:: http/tender-add-lot.http :code:
Also you will need to update data about item's related lots:
.. http:example:: http/tender-add-relatedLot-to-item.http :code:
At first we needed to add EXCLUSION criteria to our tender(:ref:`About criteria you can read here<criteria_operation>`).
.. http:example:: http/add-exclusion-criteria.http :code:
After adding needed criteria we can activate our tender, so let's do that:
.. http:example:: http/tender-activating.http :code:
Let's see what listing of tenders reveals us:
.. http:example:: http/active-tender-listing-no-auth.http :code:
Now We do see the internal id of a tender (that can be used to construct full URL by prepending http://api-sandbox.openprocurement.org/api/0/tenders/) and its dateModified datestamp.
Let's update tender by supplementing it with all other essential properties:
.. http:example:: http/patch-items-value-periods.http :code:
We see the added properies have merged with existing tender data. Additionally, the dateModified property was updated to reflect the last modification datestamp.
Checking the listing again reflects the new modification date:
.. http:example:: http/tender-listing-after-patch.http :code:
Procuring entity can not change tender if there are less than 7 days before tenderPeriod ends. Changes will not be accepted by API.
.. http:example:: http/update-tender-after-enqiery.http :code:
That is why tenderPeriod has to be extended by 7 days.
.. http:example:: http/update-tender-after-enqiery-with-update-periods.http :code:
Procuring entity can set bid guarantee:
.. http:example:: http/set-bid-guarantee.http :code:
.. index:: Document
Procuring entity can upload PDF files into the created tender. Uploading should follow the :ref:`upload` rules.
.. http:example:: http/upload-tender-notice.http :code:
201 Created response code and Location header confirm document creation. We can additionally query the documents collection API endpoint to confirm the action:
.. http:example:: http/tender-documents.http :code:
The single array element describes the uploaded document. We can upload more documents:
.. http:example:: http/upload-award-criteria.http :code:
And again we can confirm that there are two documents uploaded.
.. http:example:: http/tender-documents-2.http :code:
In case we made an error, we can reupload the document over the older version:
.. http:example:: http/update-award-criteria.http :code:
And we can see that it is overriding the original version:
.. http:example:: http/tender-documents-3.http :code:
.. index:: Enquiries, Question, Answer
When tender has active.tendering status and Tender.enqueryPeriod.endDate hasn't come yet, interested parties can ask questions:
.. http:example:: http/ask-question.http :code:
Procuring entity can answer them:
.. http:example:: http/answer-question.http :code:
One can retrieve either questions list:
.. http:example:: http/list-question.http :code:
or individual answer:
.. http:example:: http/get-answer.http :code:
Enquiries can be made only during Tender.enqueryPeriod
.. http:example:: http/ask-question-after-enquiry-period.http :code:
.. index:: Bidding
Tender status active.tendering allows registration of bids.
Bidder can register a bid for lot №1 with draft status:
.. http:example:: http/register-bidder.http :code:
And append responses for criteria requirements:
.. http:example:: http/add-requirement-responses-to-bidder.http :code:
and approve to pending status:
.. http:example:: http/activate-bidder.http :code:
Then bidder should upload proposal document(s):
.. http:example:: http/upload-bid-proposal.http :code:
It is possible to check the uploaded documents:
.. http:example:: http/bidder-documents.http :code:
If tender is modified, status of all bid proposals will be changed to invalid. Bid proposal will look the following way after tender has been modified:
.. http:example:: http/bidder-after-changing-tender.http :code:
Bidder should confirm bid proposal:
.. http:example:: http/bidder-activate-after-changing-tender.http :code:
Open UA procedure demands at least two bidders, so there should be at least two bid proposals registered to move to auction stage:
.. http:example:: http/register-2nd-bidder.http :code:
.. index:: Awarding, Qualification
After auction is scheduled anybody can visit it to watch. The auction can be reached at Tender.auctionUrl:
.. http:example:: http/auction-url.http :code:
Bidders can find out their participation URLs via their bids:
.. http:example:: http/bidder-participation-url.http :code:
See the Bid.participationUrl in the response. Similar, but different, URL can be retrieved for other participants:
.. http:example:: http/bidder2-participation-url.http :code:
An award can contain a milestone of type apl
.. http:example:: http/get-awards-list.http :code:
Procuring entity cannot change the status of the award before milestone.dueDate
.. http:example:: http/fail-disqualification.http :code:
During this time the bidder can upload evidence documents to his bid
.. http:example:: http/post-evidence-document.http :code:
Qualification commission registers its decision via the following call:
.. http:example:: http/confirm-qualification.http :code:
.. index:: Setting Contract
There are to modes of contracting depending on system configuration:
In regular contacting the contract will be created in tender system first.
Read more about working with regular contracting in tendering system in :ref:`old_contracting_tutorial_registration` section.
When the tender is completed (after contracts activation), contract (that has been created in the tender system) is transferred to the contract system automatically.
Read more about working with regular contracting in contracting system in :ref:`old_contracting_tutorial` section.
In EContracting the contract is created directly in contracting system.
Note
Some of data will be mirrored to tender until contract will be activated for backward compatibility.
Read more about working with EContracting in contracting system in :ref:`econtracting_tutorial` section.
Tender creator can cancel tender anytime (except when tender in status active.auction or in terminal status e.g. unsuccessful, canceled, complete).
The following steps should be applied:
- Prepare cancellation request.
- Fill it with the protocol describing the cancellation reasons.
- Passing complaint period(10 days)
- Cancel the tender with the prepared reasons.
Only the request that has been activated (4th step above) has power to cancel tender. I.e. you have to not only prepare cancellation request but to activate it as well.
For cancelled cancellation you need to update cancellation status to unsuccessful from draft or pending.
See :ref:`cancellation` data structure for details.
You should pass reason and reasonType, status defaults to draft.
There are four possible types of cancellation reason - tender was noDemand, unFixable, forceMajeure and expensesCut.
id is autogenerated and passed in the Location header of response.
.. http:example:: http/prepare-cancellation.http :code:
You can change reasonType value to any of the above.
.. http:example:: http/update-cancellation-reasonType.http
:code:
This step is required. Without documents you can't update tender status.
Upload the file contents
.. http:example:: http/upload-cancellation-doc.http :code:
Change the document description and other properties
.. http:example:: http/patch-cancellation.http :code:
Upload new version of the document
.. http:example:: http/update-cancellation-doc.http :code:
For activate complaint period, you need to update cancellation from draft to pending.
.. http:example:: http/pending-cancellation.http :code:
When cancellation in pending status the tender owner is prohibited from all actions on the tender.
if the complaint period(duration 10 days) is over and there were no complaints or all complaints are canceled, then cancellation will automatically update status to active.