Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time


The Defense open tender is plugin to Open Procurement API software.

REST-ful interface to plugin is in line with core software design principles.


This plugin conventions follow the Open Procurement API conventions.

Main responsibilities

The Defense open tender is a procedure dedicated to Ukrainian above threshold procurements for defense purposes. The code for this type of procedure is aboveThresholdUA.defense.

Business logic

The approach to Defense open tender is different from core Open Procurement API procedure (that is used for below threshold procurements) mainly in :ref:`stage that precedes <tendering>` auction. Differences are in the following aspects:

  1. Tender can be edited through the whole tenderPeriod (while in active.tendering state), but any edit that is close to tenderPeriod.endDate would require extending that period.
  2. There is no dedicated active.enguiries state.
  3. Questions can be asked within enquiryPeriod that is based upon tenderPeriod.
  4. Answers are provided during the whole tenderPeriod.
  5. Bids can be placed during the whole tenderPeriod.
  6. Placed bids are invalidated after any tender condition editing and have to be re-confirmed.

Project status

The project is in active development and has pilot installations.

The source repository for this project is on GitHub:

You can leave feedback by raising a new issue on the issue tracker (GitHub registration necessary). For general discussion use Open Procurement General maillist.

Documentation of related packages

API stability

API is highly unstable, and while API endpoints are expected to remain relatively stable the data exchange formats are expected to be changed a lot. The changes in the API are communicated via Open Procurement API maillist.

Change log


Released: not released yet

Next steps

You might find it helpful to look at the :ref:`tutorial`, or the :ref:`reference`.