/slegp/price_norms/search

POST /api/slegp/price_norms/search

Price: 40 credits

Search the price norm currently published by the Sierra Leone National Public Procurement Authority (egp.nppa.gov.sl): the reference prices of goods by region. Each row carries the item code, name, specification, unit of measure, its category, the price norm name, version and validity dates, and one price per region with its currency and country of origin.

How to use it

Every row carries all five regional prices (Western Area, Eastern, Northern, Southern, North West) in `prices`. `category` matches a category name exactly, letter case aside.

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 in the item name, specification or code (examples: "fire extinguisher", "04326"; minLength: 1)
• category string nullable — Category name or id (examples: "VEHICLES", "BUILDING MATERIALS"; minLength: 1)
• category_type string nullable — Category type (one of: "common", "special")
• count integer required — Max number of price-norm items to return (min: 1)

Response

• @type string (default: "SlegpPriceNormItem")
• code string required
• item_code string nullable
• item_id string nullable
• name string nullable
• specification string nullable
• unit_of_measure string nullable
• unit_of_measure_id string nullable
• measurement_id string nullable
• category object nullable
  • @type string (default: "SlegpPriceCategory")
  • id string required
  • name string nullable
  • description string nullable
  • category_type string nullable
  • external_code string nullable
• price_norm_id string nullable
• price_norm_name string nullable
• price_norm_version integer nullable
• valid_from_at integer nullable
• valid_to_at integer nullable
• publisher string nullable
• publisher_id string nullable
• created_at integer nullable
• prices array (default: [])
  • @type string (default: "SlegpRegionalPrice")
  • id string nullable
  • region string nullable
  • region_id string nullable
  • price number nullable
  • currency string nullable
  • country_of_origin string nullable
  • created_at integer nullable
  • updated_at integer nullable

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.