Retrieving Tender Information¶

Getting list of all tenders¶

GET /tenders HTTP/1.1

HTTP/1.1 200 OK

Sorting¶

Tenders retuned are sorted by modification time.

Limiting number of Tenders returned¶

You can control the number of data entries in the tenders feed (batch size) with limit parameter. If not specified, data is being returned in batches of 100 elements.

Batching¶

The response contains next_page element with the following properties:

offset:	This is the parameter you have to add to the original request you made to get next page.
path:	This is path section of URL with original parameters and offset parameter added/replaced above.
uri:	The full version of URL for next page.

If next page request returns no data (i.e. empty array) then there is little sense in fetching further pages.

Synchronizing¶

It is often necessary to be able to syncronize central database changes with other database (we’ll call it “local”). The default sorting “by modification date” together with Batching mechanism allows one to implement synchronization effectively. The synchronization process can go page by page until there is no new data returned. Then the synchronizer has to pause for a while to let central database register some changes and attempt fetching subsequent page. The next_page guarantees that all changes from the last request are included in the new batch.

The safe frequency of synchronization requests is once per 5 minutes.

Reading the individual tender information¶

GET /tenders/64e93250be76435397e8c992ed4214d1 HTTP/1.1

HTTP/1.1 200 OK

Reading the tender documents list¶

GET /tenders/64e93250be76435397e8c992ed4214d1/documents HTTP/1.1

HTTP/1.1 200 OK

Example request:

GET /api/2.3/tenders/a4f89b85bdc041f080c73ca5b06ee953/documents HTTP/1.0
Authorization: Basic YnJva2VyOg==
Host: api-sandbox.openprocurement.org


200 OK
Content-Type: application/json; charset=UTF-8

{
  "data": [
    {
      "description": "document description modified",
      "title": "Notice.pdf",
      "url": "http://api-sandbox.openprocurement.org/api/2.3/tenders/a4f89b85bdc041f080c73ca5b06ee953/documents/6d900d7c8e584ff99c734991cfbb7137?download=e498e2079def4c68b93b7f08cbb62743",
      "format": "application/pdf",
      "documentOf": "tender",
      "datePublished": "2016-06-10T15:29:49.569824+03:00",
      "documentType": "technicalSpecifications",
      "id": "6d900d7c8e584ff99c734991cfbb7137",
      "dateModified": "2016-06-10T15:29:49.569872+03:00"
    },
    {
      "title": "AwardCriteria.pdf",
      "url": "http://api-sandbox.openprocurement.org/api/2.3/tenders/a4f89b85bdc041f080c73ca5b06ee953/documents/2fc2e39b222b4c74b94738702188424d?download=9ef24d6aa3334caca68d2a0bf740fe09",
      "format": "application/pdf",
      "documentOf": "tender",
      "datePublished": "2016-06-10T15:29:49.993070+03:00",
      "id": "2fc2e39b222b4c74b94738702188424d",
      "dateModified": "2016-06-10T15:29:49.993111+03:00"
    }
  ]
}

Reading the tender document¶

The document can be retrieved by requesting the url returned in structures from document list request in data[*].url. It is safe to provide the download URL to end user for download.