/mtetenders/tenders

POST /api/mtetenders/tenders

Price: 5 credits

One Malta public call for tenders on etenders.gov.mt by resource id: contracting authority, procedure, directive, CPV and NUTS codes, estimated value in EUR, lots, TED notice links, the publication, clarification, submission, opening and award dates, and on archived calls the awarded economic operators and every tenderer with its submitted value.

How to use it

Takes the `id` of a mtetenders/tenders/search or mtetenders/opened_tenders/search row. Preliminary market consultations, procedures never published (negotiated procedures, simplified procedures, specific contracts, DPS specific contracts) and cancelled calls answer 412; mtetenders/opened_bids still returns their bids once the tenders are opened.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tender_id string required — Resource id of the call or its page URL (examples: "14128597", "https://www.etenders.gov.mt/epps/cft/prepareViewCfTWS.do?resourceId=14128597"; minLength: 1)

Response

• @type string (default: "MtetendersTender")
• id string required
• name string nullable
• reference string nullable
• buyer object nullable
  • @type string (default: "EppsBuyerRef")
  • id string nullable
  • name string required
• published_on_behalf_of object nullable
  • @type string (default: "EppsBuyerRef")
  • id string nullable
  • name string required
• original_buyer_name string nullable
• summary string nullable
• procurement_type string nullable
• procedure string nullable
• contract_form string nullable
• directive string nullable
• award_criteria string nullable
• threshold string nullable
• estimated_value number nullable
• currency string (default: "EUR")
• cpv_codes array (default: [])
  • @type string (default: "EppsCode")
  • code string nullable
  • name string nullable
• cpc_category string nullable
• nuts_codes array (default: [])
• is_eu_funded boolean nullable
• is_gpp boolean nullable
• has_lots boolean nullable
• lots_count integer nullable
• lot_bidding string nullable
• max_lots integer nullable
• lots array (default: [])
  • @type string (default: "EppsLot")
  • number integer required
  • name string nullable
  • estimated_value number nullable
• has_tender_structure boolean nullable
• has_e_auction boolean nullable
• accepts_multiple_tenders boolean nullable
• requires_certification_check boolean nullable
• has_post_award_review boolean nullable
• allows_notification_registration boolean nullable
• allows_clarification_uploads boolean nullable
• ted_urls array (default: [])
• published_at integer nullable
• contract_notice_at integer nullable
• clarification_end_at integer nullable
• clarification_response_deadline_at integer nullable
• invitation_deadline_at integer nullable
• submission_deadline_at integer nullable
• opening_at integer nullable
• awarded_at integer nullable
• award_notice_at integer nullable
• framework_end_at integer nullable
• first_specific_contract_at integer nullable
• awards array (default: [])
  • @type string (default: "MtetendersContractAward")
  • supplier_name string nullable
  • cpv_code string nullable
  • lot_name string nullable
  • value number nullable
  • currency string nullable
• tenderers array (default: [])
  • @type string (default: "MtetendersTenderer")
  • supplier_name string nullable
  • is_winner boolean nullable
  • lot_name string nullable
  • value number nullable
  • currency string nullable
• country string (default: "MT")
• url string required

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No public call under that resource id Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.