Licitações PNCP Brazil Tender Scraper

Scraper for Brazilian public licitações on PNCP (Portal Nacional de Contratações Públicas). Collect federal and local tenders by keyword, UF, modality and date window. Each item includes agency, object, estimated value, opening and closing dates, status and source link. Built for growth teams, agencies and analysts who track government demand in Brazil without maintaining a portal-specific collector. Collection prefers the Brainiall engine and falls back to direct HTTP that honours robots.txt, rate limits and retries. Public procurement notices only.

What it does

Provide a keyword (query), a state (uf), a modality, and/or a date window. The Actor reads PNCP result pages up to pages and stops at limit tenders. dataInicial defaults to 30 days ago and dataFinal defaults to today when omitted. Empty or blank pages are reported as errors (exit code 1). A valid empty search returns zero items and does not charge result. Local default is plan / dry-run. Live collection needs --confirm and runtime keys. Keys are never stored in files.

Why this Actor

• Tender fields, normalized. Control id, agency, UF, municipality, object, estimated value, dates, modality, status and PNCP link in one item.
• Filters that match how buyers search. Keyword against the object, UF, modality name or code (pregao_eletronico / 6), and an inclusive publication window.
• Hard cap. limit default 50 (cap 500). Page size follows the public consultation API (up to 50 per page).

Input

Field	Type	Default
query	string	—
uf	string	—
modalidade	string	—
dataInicial	string	30 days ago (YYYY-MM-DD)
dataFinal	string	today (YYYY-MM-DD)
limit	integer	50
pages	integer	1

Provide at least a keyword, UF or a date range.

{
  "query": "limpeza",
  "uf": "SP",
  "modalidade": "pregao_eletronico",
  "dataInicial": "2024-03-01",
  "dataFinal": "2024-04-30",
  "limit": 50,
  "pages": 2
}

Output

One dataset item per tender. Example taken from the Actor test fixtures:

{
  "id": "00394452000103-1-000040/2024",
  "orgao": "MUNICIPIO DE CAMPINAS",
  "uf": "SP",
  "municipio": "Campinas",
  "objeto": "Registro de preços para serviços de limpeza predial",
  "valor_estimado": 1850000.5,
  "data_abertura": "2024-03-10T09:00:00",
  "data_encerramento": "2024-03-25T17:00:00",
  "modalidade": "Pregão - Eletrônico",
  "situacao": "Divulgada no PNCP",
  "link": "https://pncp.gov.br/app/editais/00394452000103/2024/40"
}

Pricing

Pay-per-event from the Actor listing (USD):

Event	USD
result (primary)	$0.0012 per tender
run-start	$0

Worked cost example:

• 50 tenders → $0.06
• 1,000 tenders → $1.20

Failed items are not billed. No monthly minimum.

Use cases

1. Bid monitoring — watch PNCP licitações in a UF and modality for objects that match your catalog (cleaning, software, works).
2. Demand research — assemble a period of public tenders with agency, value and dates for a market brief.
3. Lead lists for agencies that sell to Brazilian municipalities and need the PNCP link on every row.

FAQ

Is this the official PNCP API? The Actor collects public notices as published on PNCP. Honor robots.txt and the portal rate limits. Do not overload the source.

What modality values work? A name or a numeric code (for example pregao_eletronico or 6). Unknown values are passed through as a filter.

Can I download an entire year of Brazil in one run? No. Cap is 500 records per run. Split by UF, keyword and date window.

Limits

• 500 records per run.
• Page size follows the public consultation API (up to 50 per page).
• Empty or blank pages are reported as errors (exit code 1). A valid empty search returns zero items.
• Public procurement notices only. Do not use the data to harass agencies or bidders. Local default is plan/dry-run.

---

Built and maintained by Brainiall.