/eopbg/tenders/search

POST /api/eopbg/tenders/search

Price: 20 credits

Search tenders on Bulgaria's EOP e-procurement system — every procedure of Bulgarian contracting authorities since 2020, below-threshold ones included — by subject, buyer name or EIK, contracted supplier name or EIK, status, contract type, procedure, CPV, NUTS region, EU funding, year and publication date, with the national unique number, buyer, estimated value, deadlines, lot and offer counts and the green/social/EU-funding flags of each tender. Newest publications first.

How to use it

Filters combine with AND; supplier_registry_number takes a company EIK as eopbg/suppliers/search returns it. status archived selects archived tenders, whose rows keep their final status such as awarded or cancelled; complex marks multi-lot tenders. Pass the id of a row to eopbg/tenders for lots, offers, contracts, notices and appeals.

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: 5000)
• keyword string nullable — Words in the tender subject (examples: "гориво"; minLength: 1)
• buyer_name string nullable — Words in the contracting authority name (examples: "община"; minLength: 1)
• buyer_registry_number string nullable — Contracting authority EIK/BULSTAT (examples: "000193371")
• buyer_batch_number string nullable — Contracting authority register number (examples: "00160")
• supplier_name string nullable — Words in a contracted supplier name (examples: "ПЕТРОЛ"; minLength: 3)
• supplier_registry_number string nullable — Contracted supplier EIK/BULSTAT (examples: "831496285")
• status string nullable — Tender status (one of: "open", "closed", "cancelled", "awarded", "paused", "complex", "archived")
• contract_type string nullable — Nature of the contract (one of: "services", "supplies", "works")
• procedure_type string nullable — Procurement procedure (one of: "private", "open_procedure", "restricted_procedure", "competitive_procedure_with_negotiation", "negotiated_procedure_with_prior_call_for_competition", "competitive_dialogue", "innovation_partnership", "accelerated_restricted", "negotiated_procedure", "accelerated_negotiated", "design_contest", "public_competition", "direct_negotiation", "collecting_offers_with_notice", "invitation_to_specific_economic_operators", "mini_competition_within_fa", "qualification_system", "dynamic_purchasing_system", "market_research", "restricted_procedure_under_qs", "restricted_procedure_under_dps", "negotiated_with_prior_invitation_for_participation_under_qs", "collect_request", "restricted_design_contest")
• cpv string nullable — Main CPV code (examples: "09100000")
• nuts string nullable — Place-of-performance NUTS code (examples: "BG411")
• eu_funded boolean nullable — Only tenders with or without EU funding
• year integer nullable — Year the tender was created (examples: 2025; min: 2000; max: 2100)
• published_from string nullable — Earliest publication date, inclusive (examples: "2026-06-01")
• published_to string nullable — Latest publication date, inclusive (examples: "2026-08-31")

Response

• @type string (default: "EopbgTenderSummary")
• id string required
• special_number string nullable
• published_tender_id string nullable
• guid string nullable
• description string nullable
• status string nullable
• stage string nullable
• participation string nullable
• procedure_type string nullable
• contract_type string nullable
• technique string nullable
• award_criterion string nullable
• buyer object nullable
  • @type string (default: "EopbgBuyer")
  • id string nullable
  • name string required
  • registry_number string nullable
  • image string nullable
• value object nullable
  • @type string (default: "EopbgValue")
  • amount number nullable
  • amount_min number nullable
  • amount_max number nullable
  • currency string nullable
• cpv array (default: [])
• dates object nullable
  • @type string (default: "EopbgTenderDates")
  • published_at integer nullable
  • deadline_at integer nullable
  • offers_deadline_at integer nullable
  • offers_start_at integer nullable
  • opening_at integer nullable
  • price_opening_at integer nullable
  • status_changed_at integer nullable
• lots_count integer nullable
• offers_count integer nullable
• parent_tender_id string nullable
• parent_special_number string nullable
• child_tenders array (default: [])
• linked_tenders array (default: [])
• eu_programme_codes array (default: [])
• eu_programme_text string nullable
• appeal_urls array (default: [])
• flags object nullable
  • @type string (default: "EopbgFlags")
  • is_eco boolean nullable
  • is_social boolean nullable
  • is_innovative boolean nullable
  • is_strategic boolean nullable
  • is_joint_procurement boolean nullable
  • is_complained_about boolean nullable
  • has_preliminary_control boolean nullable
  • has_eu_programme boolean nullable
  • is_eu_funded boolean nullable
  • has_green_criteria boolean nullable
  • has_protected_jobs boolean nullable
  • has_strategic_requirements boolean nullable
  • is_security_and_defense boolean nullable
  • is_social_service boolean nullable
  • has_appeal_proceedings boolean nullable
• country string (default: "BG")
• 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.