# Latin America Public Tenders: Colombia, Brazil, Chile & more (`cleanyield/latam-public-tenders`) Actor

Returns Latin America public tenders (licitaciones) from Colombia, Brazil, Chile, Paraguay, Uruguay: buyer, deadline, USD amount, winner. Pay per result.

- **URL**: https://apify.com/cleanyield/latam-public-tenders.md
- **Developed by:** [Clean Yield](https://apify.com/cleanyield) (community)
- **Categories:** Business, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.20 / 1,000 tenders

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Latin America Public Tenders: Colombia, Brazil, Chile & more

![Real results table from a run of the pre-filled form with the current code: open IT tenders in Colombia with the title as published, buyer, amount in USD and bid deadline](https://cleanyield-data.github.io/img/latam-tenders.png)

**For companies selling to governments in Latin America: pick a country and a sector and get open public tenders with buyer, bid deadline, English title and USD amount when stated.**

💲 **USD 8 per 1,000 tenders** (Free plan · from USD 6.20 on higher plans) (USD 0.80 per 100) · you only pay for valid results (tender IDs that don't exist and incomplete records are free) · [Lite version with no per-result charge](https://apify.com/cleanyield/latam-public-tenders-lite)

🎁 **Try it before you pay:** the [Lite version](https://apify.com/cleanyield/latam-public-tenders-lite) has no per-result charge (up to 25 tenders per run). Apify's free plan also includes $5/month to spend in the Store — that covers about 625 tenders with this Actor (USD 0.008 per tender).

### How to use the public tenders scraper

1. Pick countries and a **sector** (for example `it-software`) or type **keywords** (`ambulancia`, `ambulância`). Or paste tender IDs to look them up.
2. Click **Start**. A Colombia search with English titles takes about 8–9 seconds (measured on Apify on 2026-11-10) and a Brazil keyword search 20–26 seconds (measured 2026-11-06).
3. Get one row per tender with title (also in English), buyer, status, bid deadline, amount in USD when stated and the winner once awarded. Download it as JSON, CSV or Excel, or read it through the API.

▶️ **Click Start: the form is pre-filled with open IT and software tenders published in Colombia in the last 5 days and usually finishes in about 10 seconds** (8–9 s in 3 runs on Apify on 2026-11-10; costs about USD 0.12).

![Animation built from a real run: the public Apify Store page (real screenshot), then the input of the pre-filled form, Start and the results of that run (rendered from the real run data, not screenshots of Apify Console)](https://cleanyield-data.github.io/img/latam-tenders-run.gif)

#### What the demo returns

Real output of the pre-filled demo, run on Apify on 2026-11-08 (15 tenders in 11 seconds; re-run on 2026-11-10 with the current version: 15 tenders in 8–9 seconds, all with a USD amount and an English title; amounts move a little with the exchange rate):

| Tender (English title, as returned) | Buyer | Amount (USD) | Bids close | Procedure |
|---|---|---|---|---|
| PROVISION OF CORPORATE NETWORK TELECOMMUNICATIONS SERVICES WAN-LAN; IT SECURITY AND VIDEOCONFERENCING FOR THE OFFICE OF THE ATTORNEY GENERAL… | FISCALÍA GENERAL DE LA NACIÓN NIVEL CENTRAL | 103,465,849 | 2026-11-20 | public tender |
| Acquire a subscription to the right of use, in the software-as-a-service mode, of UiPath licenses | SUPERINTENDENCIA FINANCIERA DE COLOMBIA | 205,523 | 2026-11-25 | reverse auction |
| Renewal of licensing and support for perimeter security devices, as well as email security subscriptions and EDR… | IDEP | 43,392 | 2026-11-26 | reverse auction |
| REVERSE AUCTION: COMPUTER RENTAL (Submission of offer) | ORQUESTA FILARMONICA DE BOGOTA | 38,833 | 2026-11-18 | reverse auction |
| CORRECTIVE MAINTENANCE OF COMPUTER EQUIPMENT AND PERIPHERALS FOR THE NATIONAL POLICE | DILOF | 20,903 | 2026-11-17 | small value |

One item from that run (shortened):

```json
{
  "tenderId": "CO:secop2:CO1.REQ.11325272",
  "country": "CO",
  "titleEn": "Acquire a subscription to the right of use, in the software-as-a-service mode, of UiPath licenses",
  "title": "Adquirir la suscripción al derecho al uso en la modalidad de software como servicio de licencias UIPath",
  "buyer": { "name": "SUPERINTENDENCIA FINANCIERA DE COLOMBIA", "taxId": "890999057", "city": "Bogotá" },
  "procedureType": "reverse-auction",
  "status": "open",
  "amount": { "value": 665864627, "currency": "COP", "valueUsd": 205522.99 },
  "publishedDate": "2026-11-06",
  "closingDate": "2026-11-25",
  "standardCategory": { "scheme": "UNSPSC", "segment": "43", "sector": "it-software" },
  "url": "https://community.secop.gov.co/Public/Tendering/OpportunityDetail/Index?noticeUID=CO1.NTC.11190297"
}
```

### What does the Latin America Public Tenders scraper do?

Get new **public tenders, government contracts and RFP / bid opportunities from Colombia (SECOP II), Brazil (PNCP), Chile (Mercado Público / ChileCompra), Paraguay (DNCP) and Uruguay (ARCE, beta)** in one clean, normalized format, straight from each government's official open-data API. Built for companies that sell to the government — SME suppliers, distributors, construction and IT firms, consultancies — and for the agencies and bid teams that find opportunities for them. Also works as a **PNCP API**, **SECOP II API**, **Mercado Público API** and a daily **government tender alert** for your sector.

### Why use this Latin America public procurement scraper?

- 🌎 **One Actor instead of five, every country complete**: Colombia, Brazil, Chile, **Paraguay and Uruguay (beta)** in the same output schema — same status values, same procedure types, same date and money format. Colombia with its **bid deadline**, Chile **without an API ticket**, Brazil, Paraguay and Uruguay **with the winner and amount** once awarded, Paraguay and Uruguay **with the bidding documents (pliegos)**.
- 🇬🇧 **English titles**: `titleEn` / `descriptionEn` for every tender (faithful AI translation, no extra charge), plus one `standardCategory` (UNSPSC segment + sector) that means the same in every country.
- 🎯 **Your sector, ready-made**: 15 sector packs (IT, construction, cleaning, security, medical, food, vehicles…) with Spanish **and** Portuguese keywords (accents ignored) plus UNSPSC codes, so "every new tender of my sector" works on the first run.
- 🧹 **Clean, normalized output**: buyer name and tax ID (NIT / CNPJ / RUT with check digit), region, UNSPSC category with English segment name, ISO currency + indicative **USD value**, normalized `status` and `procedureType` (plus the original text), stable `tenderId`.
- 🕒 **Correct deadlines**: exact UTC times *and* the local time shown on the portal (Colombia publishes the date only). Chile's API labels local time as "Z" (UTC); taken literally, every Chilean deadline would be off by 3–4 hours — we convert it right.
- 🔁 **Monitor included**: schedule it and get only new tenders, plus tenders you already got whose **deadline was extended**, that were **awarded (winner + amount)**, cancelled or whose amount changed. Slack or webhook alerts, **filtered by sector, country and minimum amount** if you want.
- 🚫 **No noise from direct awards**: ~90% of SECOP II records are direct contracts nobody can bid on; by default you only get competitive procedures.
- ⚡ **Fast**: measured on Apify on 2026-11-06, Brazil keyword searches in 20–26 s (they used to take minutes), Colombia in ~5 s, a 3-country keyword search in under a minute; sync mode for Clay, n8n and Make.
- 🤖 **AI-agent ready**: pay-per-result only (no usage fees), works through MCP without an Apify account.
- 🏛️ **Official open data**: datos.gov.co (SODA API), PNCP (portal search and consultation API), Mercado Público OCDS API, DNCP Paraguay OCDS API and ARCE Uruguay OCDS open data, the channels each government publishes for reuse.

#### This Actor vs typical alternatives

Measured head-to-head with the same 3 keyword searches from our fixed test set (Colombia "vigilancia" and "software", Brazil "ambulância"): a multi-country LATAM tender alternative run on Apify on 2026-11-05, and this Actor re-measured on 2026-11-06 against the same official sources. Chile could not be compared: the alternative needs a personal API ticket set as an environment variable.

| Same 3 searches | Typical alternative (measured) | This Actor |
|---|---|---|
| Countries in one output schema | CO, BR (+ CL only with your own API ticket) | **CO, BR, CL (no ticket), PY, UY** |
| Useful fields filled (14 per tender) | 77% | **85%** |
| Colombia bid deadline | 0 of 50 | **✓ when published (`closingDate`)** |
| Amount in USD | ✗ | **✓** |
| Status correct (direct awards with a supplier already selected are not "open"; checks on the tenders both returned) | 160 / 177 | **177 / 177** |
| Detail link | sometimes the SECOP login page | **public tender page** |
| Results for Brazil "ambulância", last 7 days | 2 | **25 (the maximum asked)** |
| Run time on Apify, Brazil keyword search (7 days) | 80 s | **20–26 s** |
| Run time on Apify, Colombia searches | **3 s** | 5 s (8–9 s with English titles, measured 2026-11-10) |
| Winner and amount (when awarded), bidding documents | ✗ | **✓** |
| English titles, one category for every country | ✗ | **✓ (`titleEn`, `standardCategory`)** |
| Cost per 1,000 biddable tenders | ~USD 23 (USD 4 per 1,000 rows, about 9 in 52 Colombian rows biddable) | **USD 8 (only biddable tenders by default)** |
| Monitor mode: new tenders + deadline/award/amount changes, Slack/webhook | new/changed only | **✓ with re-checks and alert rules (sector, country, minimum amount)** |

#### Measured quality

Measured on 2026-11-06 on a fixed test set of **61 real inputs** (31 tender-ID lookups in the five countries — single tenders whose expected values were taken from each portal's official API record, queried separately, plus one 3-country lookup —, 4 IDs that don't exist, and 26 searches by sector, keyword, buyer, region, status, amount and dates):

| Metric | Result | Target |
|---|---|---|
| Successful runs | **100%** | ≥ 99% |
| Results with every required field | **100%** | ≥ 98% |
| Key fields correct (title, buyer tax ID, amount, deadline in local and UTC time, status, procedure, category) | **100%** | ≥ 99% |

Every change to the output is listed in the [CHANGELOG](https://apify.com/cleanyield/latam-public-tenders/changelog). The test set is re-run before every release.

### Use cases

- **Daily sector alerts for suppliers**: "every new open tender for IT / cleaning / medical supplies in Colombia, Brazil, Chile, Paraguay and Uruguay above USD 50,000", straight to Slack, email or your CRM.
- **Bid teams and consultancies**: a pipeline of opportunities for several clients, deduplicated by `tenderId`, with deadlines in local and UTC time.
- **Competitive intelligence**: who wins in your sector (`status: awarded` + awardees with tax ID and amount) and which buyers buy what you sell.
- **Track the tenders you are bidding on**: deadline extensions, awards and cancellations, by ID.
- **Market research**: count and size public demand by sector, buyer, region and procedure type across five countries, with one shared category (`standardCategory`).

### What data can you get?

| Field | Example | Source |
|---|---|---|
| `tenderId` | `BR:pncp:88124961000159-1-000131/2026` (stable: `country:source:id`) | This Actor |
| `country` / `source` / `language` | `BR` / `pncp` / `pt` | This Actor (the portal it was read from) |
| `title` / `description` | `REGISTRO DE PREÇOS PARA AQUISIÇÃO DE APARELHOS DE AR-CONDICONADO` | Official portal, as published |
| `buyer` | `{ "name": "MUNICIPIO DE SANTANA DO LIVRAMENTO", "taxId": "88124961000159", "taxIdType": "CNPJ", "region": "RS", "city": "Sant'Ana do Livramento" }` | Official portal |
| `categories` | `[{ "scheme": "UNSPSC", "code": "43231512", "description": "Software de gestión de licencias", "segmentName": "Information Technology Broadcasting and Telecommunications" }]` | Official portal (UNSPSC, where the country uses it) |
| `procedureType` / `procedureTypeOriginal` / `competitive` | `reverse-auction` / `Pregão - Eletrônico` / `true` | `procedureTypeOriginal` from the portal; the other two deduced |
| `status` / `statusOriginal` | `open` / `Divulgada no PNCP` (also `closed`, `awarded`, `cancelled`, `unsuccessful`, `suspended`) | `statusOriginal` from the portal; `status` deduced |
| `amount` / `awardedAmount` | `{ "value": 1267639.03, "currency": "BRL", "valueUsd": 231064.21 }` | Official portal; `valueUsd` deduced with the exchange rate of the day |
| `publishedDate` / `publishedAt` | `2026-11-03` / `2026-11-03T03:01:11.000Z` | Official portal |
| `closingDate` / `closingAt` / `closingAtLocal` | `2026-11-18` / `2026-11-18T12:00:00.000Z` / `2026-11-18T09:00:00` | Official portal; UTC and local time deduced from the time zone |
| `timezone` | `America/Sao_Paulo` | Deduced from the country and region |
| `awardees` | `[{ "name": "DFER DISTRIBUIDORA DE FERRAGENS LTDA", "taxId": "23143410000197", "taxIdType": "CNPJ", "amount": { "value": 6258, "currency": "BRL" } }]` | Official portal |
| `url` / `documentsUrl` / `biddingSystemUrl` | official tender page, documents, e-procurement system where bids are submitted | Official portal |
| `items` / `documents` | line items (quantity, unit, category, estimated value) and document links (optional) | Official portal |
| `matchedKeywords` | `["software", "licencias de software"]` | This run (your keywords and sectors) |
| `titleEn` / `descriptionEn` | `PRICE REGISTRATION FOR THE PURCHASE OF AIR-CONDITIONING UNITS` (null if the AI is not available) | AI translation |
| `standardCategory` | `{ "scheme": "UNSPSC", "code": null, "segment": "40", "sector": "energy", "sectorLabel": "…", "source": "inferred" }` | UNSPSC from the portal, or deduced from the title (`source: "inferred"`) |
| `alert` | monitor mode with alert rules: `true` if this tender was sent to Slack/webhook | This run (your alert rules) |
| `changeType` / `changes` | monitor mode: `changed` / `[{ "category": "deadline", "note": "deadline extended by 7 days" }]` | This run (monitor) |

**Source**: *Official portal* = the open-data API of SECOP II (Colombia), PNCP (Brazil), Mercado Público (Chile), DNCP (Paraguay) or ARCE (Uruguay); *Deduced* = worked out from those values with fixed rules, no AI; *AI translation* = English text written by AI.

### How much does it cost to get Latin American public tenders?

**The price depends on your Apify plan.** Higher Apify plans pay less per result, so the price shown at the top of the Store page can be another plan's price. Main result, per 1,000 tenders:

| Your Apify plan | Price per 1,000 tenders |
|---|---|
| Free | USD 8 |
| Starter (Bronze) | USD 7.40 |
| Scale (Silver) | USD 6.80 |
| Business (Gold) and higher | USD 6.20 |

Pay per result (pay per event), with no subscription or platform usage fees. IDs that don't exist or incomplete records are free. Predictable price: **USD 0.008 per tender** (Apify subscribers pay less: USD 0.0074 Bronze, 0.0068 Silver, 0.0062 Gold). At the start of every run the log says the maximum the run can cost.

| Results | Cost |
|---|---|
| 100 tenders | USD 0.80 |
| 1,000 tenders | USD 8 |
| 10,000 tenders | USD 80 |
| Pro mode (`pro-result`) | + USD 6 per 1,000 tenders (USD 0.006 each) |
| Dashboard, saved lists, monitor re-checks | Free |

Example: a supplier monitoring IT tenders in Colombia, Brazil and Chile gets ~40–80 new tenders a day → about USD 0.50–1 per day; days with no news cost nothing. Set **Maximum cost per run** and the Actor stops exactly there.

### Limits

- **5 countries**: Colombia, Brazil, Chile, Paraguay and Uruguay. Uruguay is in beta: if its source does not answer, it is skipped within seconds and nothing is charged for it. Argentina, Mexico, Peru and Ecuador are not covered.
- **Colombia arrives 1–4 days late** in its open data and publishes dates without the hour.
- **Some fields depend on the country**: Brazil does not use UNSPSC, about half of Chilean tenders have no estimated amount, and Uruguay never publishes the estimated amount or buyer tax IDs. Missing values are `null`.
- **Competitive procedures only by default**: direct contracts are left out unless you set `procurementScope` to `all`.
- **USD amounts are indicative** (exchange rate of the day). English titles are AI translations, `null` if the AI is not available.
- **Never charged:** IDs that don't exist and incomplete records. **Maximum cost per run** stops the run exactly there.

### FAQ

#### Is it legal to use this public procurement data?

Yes. Public procurement is public by law in these countries and the Actor only uses the official open-data channels: Colombia's SECOP II dataset on datos.gov.co (license CC BY-SA 4.0, published by Colombia Compra Eficiente), Brazil's PNCP portal search and consultation API (Lei 14.133/2021, art. 174), Chile's Mercado Público OCDS API (CC0), Paraguay's DNCP OCDS API (CC BY 4.0) and Uruguay's ARCE OCDS open data. It never reads protected pages and keeps a polite request rate. Awardees can be individuals (sole traders): by default their names and IDs are hidden (`awardeeData`); buyer contact names are never collected.

#### Which countries are covered? What about Argentina, Mexico, Peru and Ecuador?

Colombia, Brazil, Chile, Paraguay and Uruguay, with live official APIs (leave `countries` empty for CO, BR and CL; add `PY` and `UY` to include them). **Uruguay is in beta**: its source sometimes does not answer from Apify's servers; when that happens Uruguay is skipped within seconds, the other countries are delivered and nothing is charged for Uruguay. Its API also has no keyword search, so each new call is read one by one: keep its date window short (1–7 days, ideal for a daily monitor). Chile is also read tender by tender: keyword searches stop after 30 s with the newest matches (monitor mode keeps going where it stopped). Argentina (COMPR.AR) only offers HTML search pages that need fragile ASP.NET postbacks, and its open-data files stop in 2020; Mexico's ComprasMX requires a reCAPTCHA token; Peru's SEACE blocks cloud servers; Ecuador's open-data API answers but takes 18–40 s per request and timed out in our tests. We don't bypass access controls, so they are not included yet — vote for them in the Issues tab.

#### How fresh is the data?

Brazil (PNCP), Chile (Mercado Público), Paraguay (DNCP) and Uruguay (ARCE) are read live. Colombia's SECOP II open dataset is refreshed daily but tenders appear with a 1–4 day delay (with their original publication date — keep a 7-day window in monitor mode), and it only publishes dates (no time of day): `closingDate` is set, `closingAt` is null. Each item has `sourceUpdatedAt` and `scrapedAt`.

#### Why are some fields empty in some countries?

Because the source doesn't publish them, never because we guessed: Brazil doesn't classify tenders with UNSPSC (use keywords or sectors; `standardCategory` still gives the sector deduced from the title, marked `inferred`); most open tenders in Colombia have no UNSPSC code in the open data; about half of Chilean tenders don't publish an estimated amount; Uruguay never publishes the estimated amount (the awarded amount is there) nor buyer tax IDs. Missing values are `null`, never invented.

#### Why don't I see direct contracts?

By default (`procurementScope: competitive`) you only get procedures any supplier can bid on. Set `procurementScope` to `all` to include direct awards, exemptions (dispensa / inexigibilidade, contratación directa), requests for information and asset sales.

#### What happens if a source fails or a tender comes back incomplete?

Requests are retried automatically with backoff (Brazil's PNCP often times out). If one country is down, results from the other countries are still delivered and the failure is reported in the run log and `RUN_STATS`. Incomplete records and IDs that don't exist are skipped and **you are not charged**.

#### Will the output format change?

No. The output schema is stable and versioned (`schemaVersion: 3`: version 2 only added the Pro mode fields, version 3 only added `titleEn`, `descriptionEn`, `standardCategory`, `alert` and two countries); fields are only added, never renamed, and every change is announced in the [CHANGELOG](https://apify.com/cleanyield/latam-public-tenders/changelog) first.

#### Is this an official government product?

No. Not affiliated with or endorsed by SECOP II / Colombia Compra Eficiente, PNCP, Mercado Público / ChileCompra, DNCP, ARCE or any government agency; their names only describe the official open data this Actor reads.

#### Is there a free version or a free trial?

Yes, two ways. The Lite version has no per-result charge: up to 25 results per run, no monitor mode or alerts, and only Apify's platform usage applies. For this full version, the USD 5 of monthly credit in Apify's free plan covers about 600 tenders at the base price, and you only pay for valid, complete results.

[Open the Lite version](https://apify.com/cleanyield/latam-public-tenders-lite).

### Related Actors: if you use this, you'll also like…

- [Company Enrichment from Website: Emails, Phones & Tech](https://apify.com/cleanyield/company-enrichment-from-website) — enrich the companies that win tenders (the awardees) with website emails, phones and social profiles.

Every Clean Yield Actor has the same rules: one clean row per result, you only pay for valid results, and a Lite version with no per-result charge to try it first. All of them: [apify.com/cleanyield](https://apify.com/cleanyield).

### Support

Found a bug or need a feature? Open an issue in the **Issues** tab: we usually answer within 12 hours. Need a custom version (another source, extra fields, a different output format)? Describe it in an issue and we will tell you if we can build it.

Did this Actor help you? A [short review on Apify](https://apify.com/cleanyield/latam-public-tenders/reviews) helps other users find it (and tells us what to improve).

### Technical documentation

Everything below is reference: a complete output item, monitor mode, Pro mode, the dashboard, saved watchlists, every input field, switching from other scrapers, code examples, use inside your own Actor, migration and AI agents.

### Output example

Real item from a run on 2026-11-04 (Chile, awarded; deadline converted from Chilean local time to UTC; description shortened):

```json
{
  "schemaVersion": 2,
  "tenderId": "CL:mercadopublico:1028-40-LP26",
  "country": "CL",
  "source": "mercadopublico",
  "sourceId": "1028-40-LP26",
  "referenceNumber": "1028-40-LP26",
  "ocid": "ocds-70d2nz-1028-40-LP26",
  "title": "Servicio de Vigilancia Santos Ossa",
  "description": "La Dirección de Vialidad Región de Valparaíso requiere contratar el servicio de vigilancia para maquinarias, vehículos, bodegas y equipos que se resguardan en el recinto fiscal Campamento Santos Ossa.",
  "buyer": {
    "name": "MINISTERIO DE OBRAS PUBLICAS DIREC CION GRAL DE OO PP DCYF",
    "unit": "Dirección de Vialidad - V Región - Dirección Regional",
    "taxId": "61202000-0",
    "taxIdType": "RUT",
    "sourceId": "2024",
    "region": "Región de Valparaíso",
    "city": null
  },
  "categories": [
    {
      "scheme": "UNSPSC",
      "code": "92101501",
      "description": "Servicios de vigilancia",
      "segment": "92",
      "segmentName": "National Defense and Public Order and Security and Safety Services"
    }
  ],
  "procedureType": "public-tender",
  "procedureTypeOriginal": "Licitación Pública Mayor 1000 UTM (LP)",
  "competitive": true,
  "status": "awarded",
  "statusOriginal": "Adjudicada",
  "amount": {
    "value": 108000000,
    "currency": "CLP",
    "valueUsd": 110416.73,
    "original": "108000000"
  },
  "awardedAmount": {
    "value": 89880000,
    "currency": "CLP",
    "valueUsd": 91891.25,
    "original": "89880000"
  },
  "publishedDate": "2026-06-11",
  "publishedAt": "2026-06-11T15:34:00.000Z",
  "closingDate": "2026-06-22",
  "closingAt": "2026-06-22T19:01:00.000Z",
  "closingAtLocal": "2026-06-22T15:01:00",
  "awardedDate": "2026-06-25",
  "timezone": "America/Santiago",
  "url": "https://www.mercadopublico.cl/Procurement/Modules/RFB/DetailsAcquisition.aspx?idlicitacion=1028-40-LP26",
  "documentsUrl": "https://www.mercadopublico.cl/Procurement/Modules/Attachment/ViewAttachment.aspx?enc=1jbVauEeSrExKN9RwilbnS3n%2fFBmBxWfBHr9nFMcFblkJaOsA52VhUd%2b5VBpsEf%2bv7maThOrBU%2fwHNV%2b0mEz3n5T3Vj9grKK5El1DmoNzC4wGDfFIENlOszy8Zgd%2fUU%2be5ZveYWyxXmGAE04nMa1XlvYQmWKcz1EgDmt3GnQVtagJpIFdzAbFjHLd%2bFNuUFE%2bYvwM2i2PizhBAphUfq%2fP5MGfrV8TlZmaZG9wqUXdwRhvjNcCEjgKZ0kUT%2f6QZl%2bumn2ewCmgroJuJG6NNyNjhnbshD0%2bB66Am9zTu%2bRCMj9FZ92wbmaLJvVeSLT5joQ",
  "biddingSystemUrl": null,
  "awardees": [
    {
      "name": "JORCOR SPA",
      "taxId": "77932497-4",
      "taxIdType": "RUT",
      "isIndividual": false,
      "amount": {
        "value": 89880000,
        "currency": "CLP",
        "valueUsd": 91891.25,
        "original": "89880000"
      }
    }
  ],
  "items": null,
  "documents": null,
  "titleEn": "LICENSE RENEWAL FOR THE DOCUMENT MANAGEMENT SOFTWARE",
  "descriptionEn": null,
  "standardCategory": { "scheme": "UNSPSC", "code": "43231512", "segment": "43", "segmentName": "Information Technology Broadcasting and Telecommunications", "sector": "it-software", "sectorLabel": "IT, software & computers", "source": "source" },
  "matchedKeywords": [],
  "language": "es",
  "sourceUpdatedAt": "2026-06-11T15:34:00.000Z",
  "scrapedAt": "2026-11-04T22:55:34.341Z",
  "fitScore": null,
  "fitFactors": null,
  "daysToClose": null,
  "urgency": null,
  "buyerProfile": null,
  "whyNow": null,
  "insight": null,
  "alert": null
}
```

With Pro mode the same tender also gets, for example: `"fitScore": 55, "fitFactors": [{ "code": "sectorKeywordInTitle", "points": 45, "detail": "Sector IT, software & computers: \"licenciamiento\" in the title" }, ...], "daysToClose": 6, "urgency": "high", "buyerProfile": { "basis": "monitor", "since": "2026-10-01", "tendersPublished": 4, "typicalAmountUsd": 65000, ... }, "whyNow": "Closes in 6 day(s) (2026-11-10): prepare the bid this week."`.

### Schedule it: monitor public tenders and get only what changed

1. Pick your **sectors** and/or **keywords** (and optionally regions, buyers, minimum amount), keep **Published in the last N days** at `7` (Colombia's open data arrives a few days late; the overlap is free because already-sent tenders are not charged again).
2. Turn on **Monitor mode** (optionally give it a **Monitor state name**, e.g. `it-tenders-daily`).
3. Add a Slack webhook or a webhook URL (Zapier, Make, n8n — use it to send emails too) for alerts. Optional **alert rules**: `alertCountries`, `alertSectors` and `alertMinAmountUsd` (e.g. only medical tenders in Paraguay above USD 50,000 ping you; the dataset still has everything, with `alert: true/false`).
4. Open **Schedules** → **Create schedule** → daily → select this Actor with your input.

Each run compares with the previous one and outputs only **new tenders** and **tenders you already received that changed**: deadline extended or moved earlier, awarded (with winner and amount), cancelled, suspended, declared unsuccessful, or estimated amount changed. Each item has `changeType` (`new` / `changed`) and `changes` (`[{ field, category, previous, current, note }]`). You pay only for those. The first run is the baseline (everything is `new`). Tenders you already received are re-checked every run (up to `maxTrackedRechecks`, free) even after they leave the date window. A `MONITOR_SUMMARY` record counts new and changed tenders by category.

Ready-made inputs for 15 sectors: see `templates/alert-inputs-by-sector.md`.

### Pro mode: fit score, urgency, buyer profile and why-now

One checkbox (`proMode: true`) turns every tender into a bid decision. Each item gets:

| Field | What it tells you |
|---|---|
| `fitScore` (0–100) + `fitFactors` | How well the tender matches what you sell. Transparent sum of points, each with its reason: your keyword in the title (+45, +10 per extra keyword), a sector word in the title (+45) or only in the category (+30), main UNSPSC category in your sector or codes (+15 to +35), priority keyword (+15), open competition (+5), published budget (+5); minus points for direct procurement (−15), closing in under 2 days (−15) or under 5 days (−5), or not open anymore (−30). Sort by it, or set `minFitScore` to skip (and not pay for) weak matches. |
| `daysToClose` + `urgency` | Days left to bid (1 decimal when the exact time is known) and `critical` (≤ 2 days), `high` (this week), `normal` or `closed`. |
| `buyerProfile` | From your own monitoring history: how many tenders matching your search this buyer published since you started monitoring, its typical (median) and largest budget in USD, this tender vs its typical (`amountVsTypical`), and `recurringBuyer` (3+). Without monitor mode it covers this run only (`basis: "thisRun"`). Nobody else has this data: it grows with every day you monitor. |
| `whyNow` | The dated reason to look at it today: "Closes in 1 day(s) (2026-11-05): last chance to bid", "Deadline extended by 7 days (now closes 2026-11-20)", "Budget USD 231,064 is 3.4x this buyer's typical tender", "Just awarded to X for ~USD 110,417". `null` when there is no clear reason (never invented). |
| `insight` | One sentence written by AI (Claude Haiku) from this record's data only, e.g. "Strong match closing in 5 days; budget is twice what this buyer usually spends." |

Add `priorityKeywords` for the words that matter most to you (they are also searched as keywords). In monitor mode Pro is the same price per new/changed tender: unchanged tenders stay free.

**Price:** + USD 6 per 1,000 tenders (USD 0.006 each, `pro-result` event) on top of the base price, only for valid tenders delivered with Pro mode. If the AI sentence is not available in a run, `insight` is `null` and the price does not change (the score, urgency, buyer profile and why-now are still delivered). The run log shows the maximum cost including Pro before starting.

Without Pro mode, the end of each run tells you honestly what you missed (e.g. "5 tenders closing within 7 days flagged as urgent").

### Free dashboard in every run

Every run (Pro or not, at no extra cost) saves a shareable HTML dashboard: tenders by country and by sector, estimated budget by country in USD, top buyers and a table of **the tenders closing this week**. The link is in the `SUMMARY` record of the run's key-value store (`dashboardUrl`) and in the log. In Pro mode it adds a "best matches" table ranked by fit score.

### Saved watchlists

Give your search a name in **Saved watchlist name** (`savedListName`, e.g. `my-it-watch`): your keywords, priority keywords, sectors, UNSPSC codes, buyers and exclusions are remembered and used in every future run (scheduled or not), plus anything you add (`saveList: false` = use the list without changing it). With monitor mode, the history stays tied to the list name, so the list can grow without losing what you already received.

### Input example and configuration

#### Input example (JSON)

```json
{
  "countries": ["CO", "BR", "CL"],
  "sectors": ["it-software"],
  "status": ["open"],
  "publishedWithinDays": 5,
  "maxResults": 15
}
```

#### Configuration: all input fields

| Field | Description |
|---|---|
| `countries` | CO (SECOP II), BR (PNCP), CL (Mercado Público), PY (DNCP), UY (ARCE). Empty = CO, BR and CL. |
| `sectors` | Ready-made packs: it-software, construction, cleaning, security, medical, food, vehicles, office-supplies, consulting, telecom, energy, events-travel, training-education, uniforms-ppe, waste-environment. |
| `keywords`, `excludeKeywords` | Your own words (accents and case ignored, match the start of a word) in title, description, category or items; words that drop a tender. |
| `categoryCodes` | UNSPSC codes or prefixes of the main category (2–8 digits, e.g. `4321`). Chile always classifies; Colombia rarely for open tenders; Brazil doesn't use UNSPSC. |
| `buyers`, `regions` | Buyer name or tax ID (NIT / CNPJ / RUT); department / state (UF) / región. In Paraguay and Uruguay use the buyer name (the sources don't publish buyer tax IDs). |
| `minAmountUsd`, `maxAmountUsd` | Estimated amount range in USD (converted with today's exchange rate). |
| `status`, `procurementScope`, `procedureTypes` | open (default), closed, awarded, cancelled, unsuccessful, suspended; competitive only (default) or all; reverse-auction, public-tender... |
| `publishedWithinDays`, `publishedSince`, `closingFrom`, `closingTo` | Publication window (default 7 days) and bid-deadline range. |
| `tenderIds` | Look up specific tenders (CO1.REQ.…, PNCP control number, Mercado Público code, Paraguay ocid `ocds-03ad3f-…`, Uruguay `UY-<purchase id>`). |
| `maxResults` | Cap of tenders per run (shared fairly between countries). |
| `includeAwardees`, `awardeeData`, `includeDetails` | Winners for awarded tenders (individuals hidden by default); line items and document links. |
| `monitorMode`, `monitorStateName`, `trackChanges`, `maxTrackedRechecks`, `notifyWebhookUrl`, `notifySlackWebhookUrl` | Monitor mode and alerts. |
| `alertCountries`, `alertSectors`, `alertMinAmountUsd` | Monitor alert rules: only matching tenders go to Slack/webhook (country AND sector AND minimum USD amount). |
| `translateToEnglish` | English title and description (`titleEn`, `descriptionEn`); on by default, no extra charge. |
| `publishedUntil` | Optional end of the publication window (YYYY-MM-DD). |
| `proMode`, `priorityKeywords`, `minFitScore` | Pro mode (fit score, urgency, buyer profile, why-now, AI insight), the words that matter most, and the minimum fit score to deliver. |
| `savedListName`, `saveList` | Saved watchlist of keywords, sectors, codes and buyers. |

### Switching from another scraper? Paste your current input as is

Common LATAM tender input names (`countries`, `keywords`, `priorityKeywords`, `dateFrom`, `dateTo`, `maxItems`, `mode: "monitor"`, `webhookUrl`, `minScore`) are accepted unchanged. Chile works without your own API ticket, and Colombia comes with the bid deadline when the portal publishes it.

| Typical field | Here |
|---|---|
| `dateFrom` / `dateTo` | `publishedSince` / `publishedUntil` |
| `maxItems` / `mode: "monitor"` / `webhookUrl` | `maxResults` / `monitorMode: true` / `notifyWebhookUrl` |
| `closeDate`, `modality`, `nativeId` | `closingDate` (+ `closingAt` UTC and `closingAtLocal` where the source gives the hour), `procedureType` + `procedureTypeOriginal`, `tenderId` |
| `buyer.id`, `value.amount`, `value.currency` | `buyer.taxId`, `amount.value`, `amount.currency` (+ `amount.valueUsd`) |

Full list in *Migrating from other scrapers*.

### Usage examples: API, Python, JavaScript and integrations

Bulk input is fine: hundreds of tender IDs or a year of tenders in one run, with polite pacing per government API, automatic retries (Brazil's PNCP times out often) and your budget cap.

#### Python

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("cleanyield/latam-public-tenders").call(run_input={"sectors": ["construction"], "countries": ["CO", "CL"], "minAmountUsd": 100000})
for t in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(t["country"], t["title"], t["buyer"]["name"], t["closingAtLocal"] or t["closingDate"], t["url"])
```

#### JavaScript

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('cleanyield/latam-public-tenders').call({ countries: ['BR'], keywords: ['ambulância'], regions: ['SP'], publishedWithinDays: 7 });
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.map((t) => [t.tenderId, t.amount?.valueUsd, t.closingAt]));
```

#### Sync mode (Clay, n8n, Make, HTTP)

One HTTP call returns the results directly (typically 1–3 s for a few tender IDs; searches limited to Colombia or Brazil take a few seconds):

```
POST https://api.apify.com/v2/acts/cleanyield~latam-public-tenders/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>
Content-Type: application/json

{ "tenderIds": ["CO1.REQ.11304903", "88124961000159-1-000131/2026", "5751-39-LR26"] }
```

#### n8n and Make

Ready-made templates in this Actor's `templates/` folder: daily sector tenders → Slack (n8n), new tenders → Google Sheets deduplicated by `tenderId` (n8n), weekly email digest (Make), tender status/winner by ID (Clay) and alert inputs for 15 sectors. Or use the official Apify node/app → **Run an Actor** → `cleanyield/latam-public-tenders`.

### For developers: use it inside your own Actor

Building a procurement, B2G sales or market-intelligence product on Apify? Call this Actor as your Latin American tenders data layer:

- **Fast and synchronous**: `run-sync-get-dataset-items` returns a few tender IDs in ~1–3 s; a search limited to Colombia or Brazil takes a few seconds.
- **Stable schema**: every item has `schemaVersion` (now `3`); fields are only added, never renamed ([CHANGELOG](https://apify.com/cleanyield/latam-public-tenders/changelog)). Pro fields are always present (`null` without Pro), so your columns never move.
- **Clear price**: USD 8 per 1,000 valid tenders (+ USD 6 per 1,000 with Pro mode), no start fee, unknown IDs and incomplete records are free.

```js
import { Actor } from 'apify';

const run = await Actor.call('cleanyield/latam-public-tenders', { sectors: ['it-software'], countries: ['CO', 'CL'], proMode: true, minFitScore: 50, maxResults: 50 });
const { items } = await Actor.apifyClient.dataset(run.defaultDatasetId).listItems();
for (const t of items) console.log(t.fitScore, t.urgency, t.title, t.buyer.name, t.whyNow, t.url);
```

### Migrating from other scrapers

Coming from another Latin American tenders scraper? Paste your current input: these names are accepted as they are (if you send both, ours win).

| Their input | Ours |
|---|---|
| `countries` (`CO`, `BR`, `CL`, `PE`, `MX`, `AR`) | `countries` (also `PY` and `UY`; Peru, Mexico, Argentina and Ecuador are skipped with a warning: no reliable official open API) |
| `keywords` | `keywords` |
| `priorityKeywords` | `priorityKeywords` (+15 fit points in Pro mode) |
| `dateFrom` / `dateTo` | `publishedSince` / `publishedUntil` |
| `maxItems` | `maxResults` |
| `mode: "monitor"` | `monitorMode: true` |
| `webhookUrl` | `notifyWebhookUrl` |
| `minScore` | `minFitScore` (Pro mode) |

Not translated: `modalidades` (use `procedureTypes`: their values are not documented publicly) and `scoringWeights`. The output keeps our flat, documented field names (`tenderId`, `buyer.name`, `amount.valueUsd`, `closingAt`...): there is no "compatible output" mode because the other format nests and renames fields like `buyer` in a way that would break our stable schema.

### Use with AI agents / MCP

This Actor charges only per result (no usage fees), so AI agents can run and pay for it through the [Apify MCP server](https://mcp.apify.com) without an Apify account.

Example request to your assistant:

> "Find open government tenders for cleaning services published this week in São Paulo and Bogotá with an estimated value over USD 50,000, and tell me the buyer, deadline and link for each."

> "Which IT tenders in Colombia, Brazil and Chile close in the next 7 days and fit a company that sells software licenses and cybersecurity? Rank them and tell me why each one is worth bidding on now." (the agent runs it with `sectors: ["it-software"]`, `priorityKeywords: ["ciberseguridad"]`, `proMode: true` and sorts by `fitScore`)

> "What happened with tender 5751-39-LR26 in Chile: is it still open, was it awarded, to whom and for how much?"

Tips for agents: use `tenderIds` for lookups, `sectors`/`keywords` for searches (Spanish for CO/CL/PY/UY, Portuguese for BR); `titleEn` gives every title in English and `standardCategory.sector` groups tenders the same way in every country; `proMode: true` adds `fitScore`, `urgency` and `whyNow` to rank and explain; every item has `schemaVersion`, ISO dates, UTC `closingAt` and USD amounts; `null` means "the source has no value", never "0".

# Changelog

This Actor's version history is a separate document: https://apify.com/cleanyield/latam-public-tenders/changelog.md

# Actor input Schema

## `countries` (type: `array`):

Which official sources to search: CO = Colombia (SECOP II on datos.gov.co), BR = Brazil (PNCP, Portal Nacional de Contratações Públicas), CL = Chile (Mercado Público / ChileCompra OCDS API), PY = Paraguay (DNCP OCDS API), UY = Uruguay (ARCE OCDS open data). Leave empty for CO, BR and CL. Uruguay has no keyword search in its API (each new call is read one by one): wide date ranges are slower there. Example: \["CO", "PY"].

## `sectors` (type: `array`):

Pick your sector and the Actor matches tenders in Spanish and Portuguese for you (accents ignored), using sector keywords in the title and UNSPSC codes of the main category. Combine with your own keywords. Example: \["it-software"] finds software licences, computers, IT services in all three countries.

## `keywords` (type: `array`):

Words or phrases to find in the tender title, description, category or items (any of them matches; accents and upper/lower case are ignored; matches the start of a word, so 'licencia' also finds 'licencias'). Write them in Spanish for CO/CL/PY/UY and Portuguese for BR. Example: \["ambulancia", "ambulância", "vigilancia"].

## `excludeKeywords` (type: `array`):

Tenders containing any of these words are dropped (noise filter). Example: \["arrendamiento", "locação"].

## `categoryCodes` (type: `array`):

UNSPSC codes or prefixes (2, 4, 6 or 8 digits) of the tender's main category: 43 = IT and telecom, 4321 = computers, 72 = construction services, 80111600 = temporary staff. Chile classifies every tender with UNSPSC; Colombia rarely does for open tenders; Brazil does not use UNSPSC (use keywords). When combined with keywords, a tender matches if either matches.

## `buyers` (type: `array`):

Only tenders from these buyers: part of the name (accents ignored, e.g. 'Universidad Nacional', 'Prefeitura de São Paulo') or tax ID (NIT for Colombia, CNPJ for Brazil, RUT for Chile). Example: \["899999063", "ministerio de obras publicas"].

## `regions` (type: `array`):

Buyer location: Colombian department or city (e.g. 'Antioquia', 'Bogotá'), Brazilian state (2-letter code like 'SP' or name), Chilean region (e.g. 'Valparaíso', 'Metropolitana'). Leave empty for the whole country.

## `minAmountUsd` (type: `integer`):

Only tenders whose estimated budget (or awarded amount) is at least this many US dollars, converted from COP/BRL/CLP with today's exchange rate. Tenders without a published amount are excluded when you set this. Example: 50000.

## `maxAmountUsd` (type: `integer`):

Only tenders whose estimated budget is at most this many US dollars (e.g. 200000 for SMEs). Tenders without a published amount are excluded when you set this.

## `status` (type: `array`):

Normalized status across countries: open (accepting bids), closed (bidding closed, under evaluation), awarded, cancelled, unsuccessful (no valid bids / 'desierta'), suspended, unknown. Default: open. Leave empty for any status. Example: \["awarded"] to study who wins.

## `procurementScope` (type: `string`):

competitive (default) = only procedures any supplier can bid on: public tenders, reverse auctions (pregão, subasta inversa), small-value open calls, merit contests, restricted tenders. all = also direct awards, exemptions (dispensa, inexigibilidade, contratación directa), requests for information and asset sales.

## `procedureTypes` (type: `array`):

Optional filter by normalized procedure type, e.g. \["reverse-auction"] for pregão eletrônico / subasta inversa, \["public-tender"] for licitación pública / concorrência. Leave empty for all types in the chosen scope.

## `publishedWithinDays` (type: `integer`):

Tenders published in the last N days (default 7). Keep 7 for a daily monitor: Colombia's open data arrives with a 1–4 day delay (tenders show up later with their original publication date) and the overlap is free in monitor mode (already-sent tenders are not charged again). Ignored if 'Published since' is set. Example: 7.

## `publishedSince` (type: `string`):

Absolute start date YYYY-MM-DD (buyer's local date). Overrides 'Published in the last N days'. Example: 2026-10-01.

## `publishedUntil` (type: `string`):

Optional end date YYYY-MM-DD (buyer's local date, inclusive). Leave empty for 'up to today'.

## `closingFrom` (type: `string`):

Only tenders whose bid deadline is on or after this date (YYYY-MM-DD). Example: 2026-11-10.

## `closingTo` (type: `string`):

Only tenders whose bid deadline is on or before this date (YYYY-MM-DD), e.g. to see what closes this month.

## `tenderIds` (type: `array`):

Look up specific tenders instead of searching (search filters are ignored). Accepts the tenderId from this Actor's output or the id shown on each portal: CO1.REQ.11304903 (SECOP II), 88124961000159-1-000131/2026 (PNCP 'Id contratação PNCP'), 5751-39-LR26 (Mercado Público), ocds-03ad3f-490443-1 (DNCP Paraguay), UY-1384146 (ARCE Uruguay, 'UY-' + purchase id). Ids that don't exist are reported and not charged.

## `maxResults` (type: `integer`):

Stop after this many tenders (shared fairly between countries). Caps your cost: you pay only for tenders actually returned. In monitor mode it caps new/changed tenders. Example: 100.

## `includeAwardees` (type: `boolean`):

For awarded tenders, add who won and for how much (company name, tax ID, amount). Costs one extra request per awarded tender in Chile and a few in Brazil (still one charged result). Default on.

## `awardeeData` (type: `string`):

Awardees can be individuals (sole traders). omitIndividuals (default) hides the name and ID of natural persons and keeps companies; include keeps everything published by the government; omit removes awardee names and IDs entirely.

## `includeDetails` (type: `boolean`):

Add the line items (description, quantity, unit, category, estimated value) and, for Brazil, the list of tender documents (edital, termo de referência) with direct links. Brazil needs 2 extra requests per tender, so runs are slower. Default off.

## `translateToEnglish` (type: `boolean`):

Adds an English translation of the title and description of each tender (AI, faithful, no extra charge). Turn off to skip it. If the AI is not available in a run, the fields are null.

## `proMode` (type: `boolean`):

One checkbox for the bid-decision extras on every tender: a 0-100 fit score with its reasons (how well it matches your keywords, sectors and UNSPSC codes, and whether there is time to bid), days to close and urgency (critical = 2 days or less, high = this week), a buyer profile from your own monitoring history (tenders this buyer published since you started monitoring and its typical budget), a dated 'why now' line and a one-sentence AI insight. Charged as an extra 'pro-result' event per tender (see Pricing).

## `priorityKeywords` (type: `array`):

Words that matter most to you (also searched like normal keywords). In Pro mode a tender that mentions one gets +15 fit points. Example: \["licencias microsoft", "ciberseguridad"].

## `minFitScore` (type: `integer`):

Pro mode only: tenders with a lower fit score are skipped and not charged. Leave empty to get every match ranked by fitScore.

## `monitorMode` (type: `boolean`):

For scheduled runs: remember what was found last time and output only tenders that are new, plus tenders you already received whose deadline was extended or moved, that were awarded (with winner and amount), cancelled, suspended or declared unsuccessful, or whose estimated amount changed. Each item gets changeType (new/changed) and a changes list. You pay only for new/changed tenders. Schedule it daily.

## `monitorStateName` (type: `string`):

Optional name of the storage that keeps the previous results. Use the same name across scheduled runs to compare against them. Leave empty to derive it automatically from the rest of the input. Lowercase letters, numbers and hyphens only. Example: it-tenders-daily.

## `trackChanges` (type: `boolean`):

Monitor mode: also re-check tenders you received before (that are not awarded/cancelled yet) for deadline extensions, awards, cancellations and amount changes, even if they no longer match the date window. Default on.

## `maxTrackedRechecks` (type: `integer`):

Monitor mode: how many previously sent, still-open tenders are re-checked each run (oldest-checked first). Default 200. Re-checks are not charged; only real changes are.

## `notifyWebhookUrl` (type: `string`):

Optional. When monitor mode finds new or changed tenders, POST a JSON summary to this URL (works with Zapier, Make, n8n; use it to send emails too). Example: https://hooks.zapier.com/hooks/catch/123/abc

## `notifySlackWebhookUrl` (type: `string`):

Optional. Slack incoming-webhook URL to receive one line per new/changed tender (title, buyer, amount, deadline, link). Example: https://hooks.slack.com/services/T000/B000/XXXX

## `alertCountries` (type: `array`):

Monitor mode: send Slack/webhook alerts only for tenders from these countries (the dataset still has every new or changed tender, with alert = true/false). Example: \["CO", "PY"].

## `alertSectors` (type: `array`):

Monitor mode: alert only for tenders of these ready-made sectors (same ids as 'Sectors'). Example: \["medical", "it-software"].

## `alertMinAmountUsd` (type: `integer`):

Monitor mode: alert only for tenders whose estimated (or awarded) amount is at least this many US dollars. Tenders without a published amount do not alert. Example: 50000.

## `savedListName` (type: `string`):

Give your keywords, sectors, UNSPSC codes, buyers and exclusions a name (e.g. my-it-watch) and the Actor remembers them: next runs (scheduled or not) use the saved list plus anything you add. Pair it with Monitor mode.

## `saveList` (type: `boolean`):

Add this run's keywords, sectors, codes, buyers and exclusions to the saved list (off = use the saved list without changing it).

## Actor input object example

```json
{
  "countries": [
    "CO",
    "BR",
    "CL"
  ],
  "sectors": [
    "it-software"
  ],
  "keywords": [
    "ambulancia",
    "ambulância"
  ],
  "excludeKeywords": [
    "arrendamiento"
  ],
  "categoryCodes": [
    "4321",
    "8111"
  ],
  "buyers": [
    "899999063",
    "ministerio de obras publicas"
  ],
  "regions": [
    "SP",
    "Antioquia",
    "Metropolitana"
  ],
  "minAmountUsd": 50000,
  "maxAmountUsd": 200000,
  "status": [
    "open"
  ],
  "procurementScope": "competitive",
  "procedureTypes": [
    "reverse-auction",
    "public-tender"
  ],
  "publishedWithinDays": 7,
  "publishedSince": "2026-10-01",
  "publishedUntil": "2026-10-31",
  "closingFrom": "2026-11-10",
  "closingTo": "2026-11-30",
  "tenderIds": [
    "CO1.REQ.11304903",
    "88124961000159-1-000131/2026",
    "5751-39-LR26"
  ],
  "maxResults": 100,
  "includeAwardees": true,
  "awardeeData": "omitIndividuals",
  "includeDetails": false,
  "translateToEnglish": true,
  "proMode": false,
  "priorityKeywords": [
    "ciberseguridad"
  ],
  "minFitScore": 50,
  "monitorMode": false,
  "monitorStateName": "it-tenders-daily",
  "trackChanges": true,
  "maxTrackedRechecks": 200,
  "notifyWebhookUrl": "https://hooks.zapier.com/hooks/catch/123/abc",
  "saveList": true
}
```

# Actor output Schema

## `results` (type: `string`):

All valid results of this run (only these are charged). JSON, CSV or Excel from the dataset.

## `runStats` (type: `string`):

RUN_STATS: results saved, failures by reason (not charged), retries and success rate.

## `dashboard` (type: `string`):

DASHBOARD: a shareable HTML page with charts and rankings for this run.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "countries": [
        "CO"
    ],
    "sectors": [
        "it-software"
    ],
    "status": [
        "open"
    ],
    "publishedWithinDays": 5,
    "maxResults": 15
};

// Run the Actor and wait for it to finish
const run = await client.actor("cleanyield/latam-public-tenders").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "countries": ["CO"],
    "sectors": ["it-software"],
    "status": ["open"],
    "publishedWithinDays": 5,
    "maxResults": 15,
}

# Run the Actor and wait for it to finish
run = client.actor("cleanyield/latam-public-tenders").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "countries": [
    "CO"
  ],
  "sectors": [
    "it-software"
  ],
  "status": [
    "open"
  ],
  "publishedWithinDays": 5,
  "maxResults": 15
}' |
apify call cleanyield/latam-public-tenders --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,cleanyield/latam-public-tenders"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/JONdeSfy3GZBbtITH/builds/1XmxCFEqPexbv7wuq/openapi.json
