UK Find a Tender — Notices, Values & Deadlines

Export official Find a Tender notice records as structured JSON or CSV. Get notice and procurement identifiers, title, buyer organisation, CPV codes, the source's tender value, deadline and original notice link. Use a recent updated-date window or provide exact notice IDs.

This covers Find a Tender, not every UK procurement portal. A notice is not necessarily an opportunity open for bidding: planning notices, direct-award information, amendments and awards serve different purposes. Verify the original notice before acting.

Quick start

{"stage":"tender","daysBack":3,"maxResults":5,"maxScanned":100}

For an exact lookup:

{"noticeIds":["089792-2026"],"maxResults":1}

The example ID is a real published notice, not a promise that bidding is currently open. Exact-ID mode takes precedence over date-window mode; title and CPV filters still apply.

Filters and completeness

• stage: tender (default), planning, award or all for date-window queries.
• daysBack: 1–7 calendar dates through today, default3. Alternatively supply updatedFromDate and updatedToDate as YYYY-MM-DD, at most seven dates inclusive.
• titleContains: case-insensitive substring in the notice title.
• cpvPrefix: 2–8 digits matched against source CPV codes.
• maxResults: 1–200 paid notices, default25.
• maxScanned: 1–100 source notices examined, default100. Caps filtering cost and may end a search before all matching notices are found.

The date filter is the source API's updated-date window, not publication date. Requests cover the supplied date boundaries from 00:00:00 through 23:59:59 in the source API's date format. Returned source timestamps keep their supplied timezone offsets; the actor does not claim exact UTC window-edge semantics that the publisher documentation does not establish.

Title/CPV filtering examines only the first maxScanned unique notices encountered in the publisher’s pagination order. It is a capped feed filter, not an exhaustive search of the requested window.

Always check the free Status dataset and OUTPUT.complete. An empty result with complete:false is not proof of no matching notices. Results can be partial because of the scan, output, request, time or spending limit, or a source error.

Price

$0.005 per returned notice ($5/1,000), plus the configured $0.00005 platform start event. Five returned notices cost $0.02505. Missing/failed notices and status rows have no work-event charge. A zero-match request incurs no notice charge. Set maxResults and the Console maximum-charge limit before running.

Each distinct (ocid, noticeId) is one record. Amendments with separate notice IDs are separate records; this is a notice feed, not a consolidated latest-state view of each procurement. The same notice returned by a new run is charged again. Use recordId to deduplicate overlapping exports yourself.

Output details

Only notice records enter the default paid dataset. tenderValueAmount and currency come from tender.value; they are not inferred award spend. Values may be estimates or framework ceilings, and the actor does not infer whether VAT is included. Missing values and deadlines remain null. submissionDeadline alone does not prove bid eligibility. Contacts, suppliers, descriptions, attachments and personal profiles are excluded.

Run kaz_kakyo/uk-tender-notices through Apify's API, CLI, MCP or automation integrations. Scheduling repeats a snapshot search; no cross-run alerts or exactly-once delivery are promised.

Source: UK Open Contracting documentation. Every record carries its original notice URL and licence attribution. Contains public sector information licensed under the Open Government Licence v3.0. No government endorsement is implied.

Pseudonymous operational telemetry records actor and run IDs, run origin, timestamps, paying-plan status, a stable hashed caller identifier, and cumulative confirmed event counts. These identifiers are linkable, not anonymous. The telemetry dataset restricts unauthenticated access. Input and result content is not sent. If paid delivery is interrupted, resurrect the same run to recover pending records without another charge.

New source work has an internal three-minute budget with time reserved to save output; a larger platform timeout does not extend it. Keep run storage intact when resurrecting. Invalid saved limits stop new work after pending paid records have been recovered.