/nocopo/tenders/search

POST /api/nocopo/tenders/search

Price: 20 credits

Search the published records of the Nigeria Open Contracting Portal by free text over the project title, MDA name, ocid, package and lot numbers and budget year. Returns the record's ocid, title, MDA, package and lot numbers, budget year and publication date per row.

How to use it

There is no structured filter: a buyer, a year or a category is found by putting its words in `query`, which is a substring match over the listed columns. Rows carry no value, status, supplier or dates beyond publication — take `ocid` into nocopo/tenders for the full OCDS record. `sort: newest` orders by publication date, the default is by ocid.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Words matched against the project title, the MDA name, the ocid, the package and lot numbers and the budget year (examples: "water", "NATIONAL OIL SPILL", "116001001-000212"; minLength: 1)
• sort string — Row order (default: "ocid"; one of: "ocid", "newest")
• count integer required — Max number of records to return (min: 1; max: 5000)

Response

• @type string (default: "NocopoTenderSummary")
• id integer required
• ocid string required
• package_number string nullable
• lot_number string nullable
• budget_year integer nullable
• buyer object nullable
  • @type string (default: "NocopoBuyer")
  • id integer required
  • code string nullable
  • name string required
• published_at integer nullable
• country string (default: "NG")
• 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 — The entity was not found, or a precondition failed 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.