🔔 Brazil PNCP Tender Notices

One record per published tender notice from the keyless PNCP API — control number, agency, modality, object, proposal dates — over a bounded publication window and contracting modality, with the server total reconciled.

Public, robots-honoured, keyless.

Output is one pncp_tender_notice row per result; billing is pay-per-event, the value event being one registry record (a $0.02 start fee per run, then $0.02 per registry record). Source: pncp.gov.br.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Real rows from run Dh5e7df6kR8JLxTBh on build 0.1.11 (2026-09-18), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

control_number	modality_name	agency_cnpj	agency_name	unit_name	proposal_opens
80881915000192-1-000044/2026	Pregão - Eletrônico	80881915000192	MUNICIPIO DE LINDOESTE	Prefeitura Municipal de Lindoeste	2026-06-22T08:00:01
80881915000192-1-000045/2026	Pregão - Eletrônico	80881915000192	MUNICIPIO DE LINDOESTE	Prefeitura Municipal de Lindoeste	2026-06-30T08:00:01
80881915000192-1-000046/2026	Pregão - Eletrônico	80881915000192	MUNICIPIO DE LINDOESTE	Prefeitura Municipal de Lindoeste	2026-06-30T08:00:01
88124961000159-1-000074/2026	Pregão - Eletrônico	88124961000159	MUNICIPIO DE SANTANA DO LIVRAMENTO	PREFEITURA MUNICIPAL DE SANT´ANA DO LIVRAMENTO	2026-07-01T09:00:00
90483066000172-1-000054/2026	Pregão - Eletrônico	90483066000172	MUNICIPIO DE ANDRE DA ROCHA	MUNICÍPIO DE ANDRÉ DA ROCHA	2026-07-01T13:00:00
90871831000121-1-000023/2026	Pregão - Eletrônico	90871831000121	ESTEIO CAMARA DE VEREADORES	CÂMARA DE VEREADORES DE ESTEIO	2026-07-01T09:00:00
88243688000181-1-000058/2026	Pregão - Eletrônico	88243688000181	RIO GRANDE DO SUL ASSEMBLEIA LEGISLATIVA	ASSEMBLEIA LEGISLATIVA DO ESTADO DO RIO GRANDE DO SUL ASSEMBLEIA LEGIS	2026-07-01T09:00:00
08470342000187-1-000006/2026	Pregão - Eletrônico	08470342000187	FUNDO MUNICIPAL DE SAUDE DE ALTINHO	FUNDO MUNICIPAL DE SAUDE DE ALTINHO	2026-07-01T09:00:00

The run finished with the status message: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) — e.g. pncp_tender_notice
• control_number (string/null) — e.g. 80881915000192-1-000044/2026
• year (string/null) — e.g. 2026
• purchase_number (string/null) — e.g. PR35
• sequence (string/null) — e.g. 44
• modality_id (string/null) — e.g. 6
• modality_name (string/null) — e.g. Pregão - Eletrônico
• dispute_mode (string/null) — e.g. Aberto
• is_price_registration (boolean/null) — e.g. False
• agency_cnpj (string/null) — e.g. 80881915000192
• agency_name (string/null) — e.g. MUNICIPIO DE LINDOESTE
• unit_name (string/null) — e.g. Prefeitura Municipal de Lindoeste
• object (string/null) — e.g. CONTRATAÇÃO DE EMPRESA PARA DISPONIBILIZAÇÃO DE PROFISSIONAL MEDICO PARA EXAMES
• estimated_value (number/null) — e.g. 300543
• proposal_opens (string/null) — e.g. 2026-06-22T08:00:01
• proposal_closes (string/null) — e.g. 2026-07-07T08:00:01
• published_on (string/null) — e.g. 2026-07-01T00:00:03
• updated_on (string/null) — e.g. 2026-07-01T00:00:03
• source (string/null) — e.g. brazil-pncp-tender-notices
• release_date (string/null) — null in every sample row
• source_url (string/null) — e.g. https://pncp.gov.br/api/consulta/v1/contratacoes/publicacao?dataInicial=20260701
• observed_at (string/null) — e.g. 2026-09-18T06:28:09Z
• terminal (string/integer/null) — null in every sample row
• reported_total (string/integer/null) — null in every sample row
• raw_seen (string/integer/null) — null in every sample row
• duplicates (string/integer/null) — null in every sample row
• unique_found (string/integer/null) — null in every sample row
• delivered (string/integer/null) — null in every sample row
• scope (string/integer/null) — null in every sample row
• note (string/integer/null) — null in every sample row

What you get

One registry_record per entity, deduplicated on the source-native id. Fields the source does not publish are honest null. A run_receipt row carries the source URL, scope, reconciliation counts, and delivered/duplicate totals.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "dataInicial": "20260701",
  "dataFinal": "20260705",
  "codigoModalidadeContratacao": 6,
  "maxRecords": 50,
  "maxPages": 5
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 50 × $0.02 registry_record = $1.02 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "dataInicial": "20260701",
  "dataFinal": "20260705",
  "codigoModalidadeContratacao": 6,
  "maxRecords": 5,
  "maxPages": 5
}

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02). dataInicial narrows what the source is asked for.

3. A full-size run

{
  "dataInicial": "20260701",
  "dataFinal": "20260705",
  "codigoModalidadeContratacao": 6,
  "maxRecords": 2000,
  "maxPages": 5
}

Up to 2000 rows (the schema default for maxRecords) — about $40.02 on the Free tier ($0.02 start + 2000 × $0.02) if the source has that many.

🧾 JSON sample record

One real record from run Dh5e7df6kR8JLxTBh, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "pncp_tender_notice",
  "control_number": "80881915000192-1-000044/2026",
  "year": "2026",
  "purchase_number": "PR35",
  "sequence": "44",
  "modality_id": "6",
  "modality_name": "Pregão - Eletrônico",
  "dispute_mode": "Aberto",
  "is_price_registration": false,
  "agency_cnpj": "80881915000192",
  "agency_name": "MUNICIPIO DE LINDOESTE",
  "unit_name": "Prefeitura Municipal de Lindoeste",
  "object": "CONTRATAÇÃO DE EMPRESA PARA DISPONIBILIZAÇÃO DE PROFISSIONAL MEDICO PARA EXAMES DE ULTRASSOM",
  "estimated_value": 300543,
  "proposal_opens": "2026-06-22T08:00:01",
  "proposal_closes": "2026-07-07T08:00:01",
  "published_on": "2026-07-01T00:00:03",
  "updated_on": "2026-07-01T00:00:03",
  "source": "brazil-pncp-tender-notices",
  "release_date": null,
  "source_url": "https://pncp.gov.br/api/consulta/v1/contratacoes/publicacao?dataInicial=20260701&dataFinal=20260705&codigoModalidadeContratacao=6",
  "observed_at": "2026-09-18T06:28:09Z"
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

Charging. Each registry record is charged at the moment it is pushed (registry_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

Supply a publication window (YYYYMMDD) and a modality code. Pages are pulled to maxRecords/maxPages with 429+5xx backoff; server totalRegistros/totalPaginas reported. A transient fault after rows stops as PARTIAL; empty/page-1 fault charges nothing.

Source

https://pncp.gov.br/api/consulta/v1/contratacoes/publicacao

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Registry record (registry_record)	$0.02	$0.02	$0.02	$0.01

Worked at the live Free-tier price:

• 8 registry records: $0.02 start + 8 × $0.02 = $0.18
• 25 registry records: $0.02 start + 25 × $0.02 = $0.52
• 2000 registry records: $0.02 start + 2000 × $0.02 = $40.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50. maxRecords is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by pncp.gov.br. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (pncp.gov.br) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 2000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other NexGen Watch actors actors?
A: Same output shape and billing model; this one covers pncp.gov.br. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• Brazil CVM Public Offerings — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
• Brazil PNCP Awarded Contracts — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
• Brazil PNCP Price-Registration Minutes — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
• CMS CLIA Laboratory Registry — One structured registryrecord per record from the CMS Provider of Services File - Clinical Laboratories dataset (data.cms.gov data-api, ~681,000 rows…
• CMS Dialysis Facilities — A clean, structured roster of Medicare-certified dialysis facilities in the United States,
• CMS Hospice Facilities — A clean, structured roster of Medicare-certified hospice facilities in the United States,
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.