/ekap/direct-procurements/search

POST /api/ekap/direct-procurements/search

Price: 20 credits

Search the direct procurements (doğrudan temin) announced on Turkey's EKAP by name or description words, number, number year, procurement type, state, legal scope, province, offer deadline and announcement date, with the contracting authority, type, state, offer deadline and province of each procurement.

How to use it

Filters combine with AND; year keeps the numbers of one year, and announced_from and announced_to need announcement_type to say which announcement they date. The default order is newest number first.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of results (min: 1; max: 1280)
• keyword string nullable — Words in the direct procurement name or description (examples: "malzeme")
• number string nullable — Direct procurement number (examples: "26DT1838534")
• year integer nullable — Year of the direct procurement number (examples: 2025; min: 2022)
• contract_type string nullable — Type of procurement (one of: "goods", "works", "services", "consultancy")
• status string nullable — State of the direct procurement (one of: "announced", "evaluating", "concluded", "result_sent", "result_published")
• scope string nullable — Legal scope (one of: "under_law_4734", "exception", "out_of_scope")
• province_code string nullable — Province plate code of the contracting authority (examples: "6", "34")
• deadline_from string nullable — Earliest offer deadline, inclusive (examples: "2026-10-01")
• deadline_to string nullable — Latest offer deadline, inclusive (examples: "2026-10-10")
• announcement_type string nullable — Announcement that announced_from and announced_to refer to (one of: "procurement", "result")
• announced_from string nullable — Earliest announcement date, inclusive (examples: "2026-09-01")
• announced_to string nullable — Latest announcement date, inclusive (examples: "2026-09-10")
• sort string — Order of results (default: "number_desc"; one of: "number_desc", "number_asc", "deadline_desc", "deadline_asc")

Response

• @type string (default: "EkapDirectProcurement")
• id string required
• name string nullable
• buyer_name string nullable
• contract_type string nullable
• contract_type_code string nullable
• procurement_article string nullable
• procurement_article_code string nullable
• status string nullable
• status_code string nullable
• deadline_at integer nullable
• deadline_date string nullable
• province string nullable
• province_code string nullable
• has_announcement boolean nullable
• has_documents boolean 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.