/appal/contracts/search

POST /api/appal/contracts/search

Price: 20 credits

Search contract-signing notices of Albanian public procurement on the APP portal by subject, buyer, reference number, contract type, procedure, CPV code, estimated value range and publication date, with the contractor and its NIPT tax id, the contract value and whether it includes VAT, the estimated value, buyer, procedure, CPV codes, key dates and the signed contract documents. Newest publications first.

How to use it

Each row is one contract-signing notice and date_from/date_to bound its publication date. Pass reference_number to appal/tenders for the contract notice and winner notices of the same procedure.

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: 60)
• keyword string nullable — Words in the tender subject (examples: "karburant"; minLength: 1)
• buyer_id string nullable — Contracting authority id from appal/buyers/search (examples: "958396e0-ff24-49b3-829c-4abb6fec480a")
• cpv string nullable — CPV code with check digit (examples: "33600000-6")
• reference_number string nullable — Procedure reference number (examples: "REF-81270-04-08-2026")
• contract_type string nullable — Type of contract (one of: "works", "supplies", "services")
• procedure_type string nullable — Procurement procedure (one of: "request_for_proposal", "negotiated_without_notice", "negotiated_with_notice", "negotiated_with_notice_above_threshold", "design_contest", "small_value_purchase", "consultancy_service", "restricted", "restricted_above_threshold", "open", "open_above_threshold", "dynamic_purchasing_system", "dynamic_air_ticket_purchase", "open_simplified", "partnership_for_innovation_local", "partnership_for_innovation_international", "competitive_dialogue_local", "competitive_dialogue_international", "competitive_with_negotiations_local", "competitive_with_negotiations_international", "open_social_services_international", "open_social_services_local")
• value_min number nullable — Minimum estimated value in ALL (examples: 10000000; min: 0)
• value_max number nullable — Maximum estimated value in ALL (examples: 100000; min: 0)
• date_from string nullable — Earliest date, inclusive (examples: "2026-06-01")
• date_to string nullable — Latest date, inclusive (examples: "2026-06-30")

Response

• @type string (default: "AppalContract")
• id string required
• reference_number string nullable
• buyer object nullable
  • @type string (default: "AppalOrganisation")
  • name string required
  • tax_id string nullable
• procedure_type string nullable
• contract_type string nullable
• estimated_value object nullable
  • @type string (default: "AppalValue")
  • amount number nullable
  • currency string nullable
• cpv array (default: [])
  • @type string (default: "AppalCpv")
  • code string required
  • name string nullable
• dates object nullable
  • @type string (default: "AppalDates")
  • published_at integer nullable
  • opening_at integer nullable
  • deadline_at integer nullable
• is_suspended boolean nullable
• notice_documents array (default: [])
  • @type string (default: "AppalDocument")
  • name string nullable
  • url string required
• tender_documents array (default: [])
  • @type string (default: "AppalDocument")
  • name string nullable
  • url string required
• parent object nullable
  • @type string (default: "AppalParent")
  • id string required
  • reference_number string nullable
  • buyer object nullable
    • @type string (default: "AppalOrganisation")
    • name string required
    • tax_id string nullable
  • procedure_type string nullable
  • contract_type string nullable
  • estimated_value object nullable
    • @type string (default: "AppalValue")
    • amount number nullable
    • currency string nullable
  • cpv array (default: [])
    • @type string (default: "AppalCpv")
    • code string required
    • name string nullable
  • dates object nullable
    • @type string (default: "AppalDates")
    • published_at integer nullable
    • opening_at integer nullable
    • deadline_at integer nullable
  • notice_documents array (default: [])
    • @type string (default: "AppalDocument")
    • name string nullable
    • url string required
  • tender_documents array (default: [])
    • @type string (default: "AppalDocument")
    • name string nullable
    • url string required
• country string (default: "AL")
• supplier object nullable
  • @type string (default: "AppalOrganisation")
  • name string required
  • tax_id string nullable
• value object nullable
  • @type string (default: "AppalValue")
  • amount number nullable
  • currency string nullable
• includes_vat 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.