/ugandagpp/tenders

POST /api/ugandagpp/tenders

Price: 1 credit

One Ugandan bid invitation by id: the procuring entity, the procurement plan entry with its method, category and funding source, the estimated amount, every date of the procurement cycle from initiation to contract signature, the bid document price and security, the addresses and the cancellation state.

How to use it

`title` is the subject of the procurement plan entry and `description` is the description of work, which recent invitations leave empty. `status` is `cancelled` when a cancellation date is set, otherwise `active` or `inactive` from the portal flag. The dates after `deadline_at` are the planned schedule, not events that happened; the winning bidder is in ugandagpp/awards/search filtered by `reference_number`. The `ocid` cannot be used to look a record up.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id integer required — Bid invitation id as shown on gpp.ppda.go.ug (examples: 98312; min: 1)

Response

• @type string (default: "UgandagppTender")
• id integer required
• ocid string nullable
• reference_number string nullable
• description string nullable
• status string nullable
• buyer object nullable
  • @type string (default: "UgandagppPde")
  • id integer required
  • name string nullable
  • abbreviation string nullable
  • category string nullable
  • address string nullable
• value number nullable
• currency string (default: "UGX")
• exchange_rate number nullable
• published_at integer nullable
• deadline_at integer nullable
• country string (default: "UG")
• url string required
• financial_year string nullable
• procurement_method object nullable
  • @type string (default: "UgandagppProcurementMethod")
  • id integer required
  • code string nullable
  • name string nullable
  • description string nullable
  • bidding_period_days integer nullable
• procurement_method_justification string nullable
• plan_entry object nullable
  • @type string (default: "UgandagppPlanEntry")
  • id integer required
  • subject string nullable
  • procurement_method object nullable
    • @type string (default: "UgandagppProcurementMethod")
    • id integer required
    • code string nullable
    • name string nullable
    • description string nullable
    • bidding_period_days integer nullable
  • procurement_category object nullable
    • @type string (default: "UgandagppProcurementCategory")
    • id integer required
    • code string nullable
    • name string nullable
    • ocds_code string nullable
  • funding_source object nullable
    • @type string (default: "UgandagppFundingSource")
    • id integer required
    • name string nullable
  • estimated_amount number nullable
  • currency string (default: "UGX")
  • quantity integer nullable
  • rationale string nullable
  • has_reservation_schemes boolean nullable
• procurement_category string nullable
• funding_source string nullable
• initiated_by string nullable
• initiation_date string nullable
• confirmation_of_funds_date string nullable
• contracts_committee_approval_date string nullable
• approval_date string nullable
• invitation_to_bid_date string nullable
• pre_bid_meeting_at integer nullable
• bid_opening_at integer nullable
• bid_validity_date string nullable
• evaluation_start_date string nullable
• evaluation_end_date string nullable
• best_evaluated_bidder_notice_date string nullable
• contract_award_date string nullable
• contract_signature_date string nullable
• bid_documents_price number nullable
• bid_security_amount number nullable
• bank_name string nullable
• bank_account_number string nullable
• payment_method string nullable
• document_issue_address string nullable
• documents_inspection_address string nullable
• bid_receipt_address string nullable
• bid_opening_address string nullable
• working_hours string nullable
• has_lots boolean nullable
• has_preference_schemes boolean nullable
• has_custom_reference_number boolean nullable
• is_framework boolean nullable
• is_lotted_framework boolean nullable
• is_active boolean nullable
• is_approved boolean nullable
• is_cancelled boolean nullable
• cancelled_date string nullable
• reason_for_cancellation string nullable
• expression_of_interest string nullable
• additional_notes string nullable
• entity_procured_for string nullable
• quantity integer nullable
• created_at integer nullable
• updated_at integer nullable

Errors

• 422 — The id is not a numeric bid invitation id 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 bid invitation under that 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.