Catalog / Tenders & public contracts
TENDERS & PUBLIC CONTRACTS · TURKEY
Turkey EKAP Tenders | Turkish Public Tenders
Search Turkish public tenders on EKAP by keyword, province, tender type, status or IKN.
About this data
Search Turkish public tenders on EKAP by keyword, province, tender type, status or IKN. One row per tender with procuring entity, tender date, status and documents; add details for announcement text, OKAS codes, lots, estimated value and contract result. Daily new-only feed.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
POST /v1/tr/ekap/tenders
Turkish public tenders from EKAP: IKN, title, procuring entity, province, type, procedure, status and tender date.
Input
Send a JSON body to POST https://api.ssh.autos/v1/tr/ekap/tenders.
| Field | Type | Required | Notes |
|---|---|---|---|
keyword | string | optional | up to 200 characters |
maxItems | integer | optional | 1–5; default 3 |
Returned fields
The answer is JSON: records, a list of up to 5, and summary, the run status and counts. Each record has these 35 fields; a field the source does not publish comes back null.
35 fields per record
| Field | Type | Notes |
|---|---|---|
recordKey | string | Stable tender identity: ekap:<ikn>. Use this for upserts across runs; the sourceRecordId is a volatile detail-request handle. |
sourceRecordId | string | EKAP's per-response record id for this read, used as the detail-page handle. It can change between responses for the same tender; use ikn, not this, as the stable tender identity. |
ikn | string | Stable tender registration number (IKN), for example 2026/271215. EKAP keeps it across searches, so use it to identify and de-duplicate a tender. |
procuringEntity | string | Contracting authority (idare) that runs the tender, verbatim. |
province | string | Province the tender belongs to, verbatim in Turkish. |
tenderType | string | Tender type label exactly as EKAP shows it on the row (Mal, Yapım, Hizmet, Danışmanlık). |
tenderTypeCode | string | EKAP tender type id: 1 goods, 2 works, 3 service, 4 consultancy. |
tenderTypeLabel | string | English label for tenderTypeCode: goods, works, service or consultancy. |
procedure | string | Procurement procedure text exactly as EKAP returns it. |
procedureLabel | string | English label for procedure (open, among certain bidders, bargain 21/b) when EKAP's own enum token is one of those; otherwise null. |
procedureCode | string | EKAP procedure id when the row carries one. |
statusCode | string | EKAP tender status id as published: 1, 2, 3, 4, 5, 6, 13, 15 or 18 (for example 2 = open for participation, 18 = preliminary announcement); status carries its label. |
status | string | Tender status label exactly as EKAP shows it. |
tenderDate | string | Tender date and time (bid opening) in ISO 8601, Europe/Istanbul (UTC+03:00). |
eTender | boolean | Whether EKAP marks the tender as electronic (detail only). |
documentCount | integer | Number of tender documents EKAP lists for the row. |
documents | array of objects | Tender documents EKAP lists: id, tender id and publication date. |
publishedAt | string | Announcement date in ISO 8601 (detail only). |
announcementTitle | string | Announcement headline (detail only), verbatim. |
announcementText | string | Announcement text as plain text (detail only), first 4000 characters, verbatim. |
announcementTextTruncated | boolean | Whether announcementText was cut at the 4000-character excerpt limit (detail only). |
workLocation | string | Place where the work or delivery happens, verbatim (detail only). |
tenderPlace | string | Place where the tender is held, verbatim (detail only). |
topAuthority | string | Highest-level authority the contracting entity reports to, verbatim (detail only). |
subAuthority | string | Parent authority above the contracting entity, verbatim (detail only). |
district | string | District of the contracting entity, verbatim (detail only). |
okasCodes | array of objects | OKAS classification codes of the required items (detail only). |
lots | array of objects | Lots of a concluded tender with the bids EKAP published (detail only). |
contract | object | Contract result EKAP published for the tender (detail only). |
estimatedValue | number | Estimated value in the currency EKAP shows, when EKAP publishes one (detail only). |
estimatedValueText | string | Estimated value exactly as EKAP prints it, for example 14.608.282,00 TRY (detail only). |
currency | string | Currency code EKAP prints with the amounts, for example TRY (detail only). |
observedAt | string | When this row was read, in ISO 8601 with the UTC offset of the run. |
detailsParsed | boolean | Whether the tender's detail page was read; null when includeDetails is off. |
detailsError | string | Why the detail page could not be read, or null. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/tr/ekap/tenders -m POST -b '{"maxItems": 2}'The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: Turkey EKAP Tenders Scraper | Turkish Public Tenders. Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt