Compras.gov.br Multi-CATMAT Price History Export
Pricing
$1.50 / 1,000 price lines
Compras.gov.br Multi-CATMAT Price History Export
Export Brazilian Compras.gov.br historical material prices for multiple known CATMAT codes. Raw item prices, quantities, packaging, separate source dates and explicit coverage for spreadsheets and APIs.
Pricing
$1.50 / 1,000 price lines
Rating
0.0
(0)
Developer
h ichi
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Send up to five known Brazilian CATMAT material codes and get raw purchase-item price histories in one flat table for your spreadsheet or database. Keep Portuguese source text, original units, package capacity, quantities and separate purchase/result/update dates. Independent tool, not affiliated with the Brazilian government.
Input
catalogCodes:1–5 numeric CATMAT material codes as strings, default["443435","269520"]. lookbackDays:1–1095, default365 calendar days ending today in UTC−03:00. Optional dateFrom and dateTo must both be YYYY-MM-DD and override rolling days, max1095 inclusive days. maxItemsPerCode:1–100, default100. Each code inspects one page of100: at most500 unique rows/run. Source order is not guaranteed newest-first. More than100 source matches for a code means partial coverage; narrow the date window or split saved inputs for larger histories. This reads the public Compras.gov.br price API only.
Output
One flat row per unique validated source purchase-item price snapshot, suitable for JSON or CSV export. Source IDs are exact decimal strings, including large integers and supplied leading zeros; configure Excel identifier columns as text to avoid its automatic rounding. Material code/description, positive unitPrice, nullable quantity, supply unit/capacity, measure unit, SISPP/SISRP form, agency/state, five separate source date fields plus optional factUpdatedAt, exact API sourceUrl and observedAt. Supplier names/identifiers and personal contacts are excluded. Price lines are provided without calculated statistics or suggested bids. Free-text cells that begin with =, +, - or @ after leading whitespace gain a leading apostrophe for spreadsheet safety. spreadsheetEscapedColumns lists affected columns; DB users can remove exactly that added character from those columns. Text is already contact-minimized; original raw text is not retained.
The API has no per-row currency field: currency is null; currencyContext=BRL describes the official system's R$ convention. No FX conversion. A FR bottle with capacity5ML is not a one-ML price;0/null capacity stays0/null. Prices can represent registrations or procurement results rather than settled expenditure. Updates are not interpreted as order/payment dates. This covers material histories recorded in Compras.gov.br, not all Brazilian procurement or current bid availability. Official update frequency is not guaranteed.
Pricing
$0.0015 per unique valid price line confirmed delivered (price-line-delivered). The Actor requests one charge per valid price line accepted for delivery; an interrupted or unacknowledged batch may leave rows and charges that need reconciliation. Missing codes and withheld rows are uncharged. Default at most200 rows costs$0.30; maximum500 costs$0.75. Each new run bills delivered snapshots again; no persistent cache. Spending caps can deliver a prefix. Null, nonfinite or nonpositive prices are withheld and counted without charge. All-zero eligible results fail NO_MATCHES without charged output.
Limits
Normal HTTPS, no login/key/proxy;256MB;1second request pace;20attempts including robots/retries;150second acquisition deadline;15seconds/request;2MiB/body;8MiB aggregate decoded source bytes. The300second run allocates up to20seconds to startup,150seconds to source,100seconds to delivery,20seconds to final reports and10seconds to SDK exit. Source rows are fully staged and validated before charging. Runtime source/parse/byte/time failures produce no stored rows or price events. Planned item caps return explicit partial coverage. Source metadata and page counts must be consistent; any observed drift or conflicting duplicate identity fails staged acquisition rather than claiming complete.
Delivery uses at most10 batches of50, with batch-level progress rather than per-row report writes. Remaining time or spending limits stop before another batch and mark partial delivery. SDK writes and charging are not atomic: an acknowledgement or report failure can leave earlier rows delivered/charged. Do not blindly retry an ambiguous run. COVERAGE reports per-code source totals, withheld rows, caps, staged and confirmed-delivered counts; SUMMARY counts confirmed delivery, not attempted rows.
Privacy
Supplier names and identifiers, CPF/CNPJ, contacts, private addresses and QSA are omitted. Public agency/city/state and material facts are retained. Obvious emails/phones/CPF are removed from permitted free text; this is contact minimization, not guaranteed anonymization. No raw bodies or live personal-name fixtures are stored. Official source/API and data-use notices apply; site-content licensing is not asserted to license all API data. Retain source attribution; no redistribution permission or endorsement is claimed. Raw research input does not certify procurement/legal compliance or comparable prices.
