licitacoes-e.com APIlicitacoes-e.com ↗
Access Brazilian public tender data from Banco do Brasil via the Licitacoes-e API. Query tender statuses, buyers, and detailed procurement information.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/e2b1e608-8a0f-41c0-ab26-fa94f6f57cbe/list_all_statuses' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns the list of possible tender statuses (Situação da licitação). Use these codes as the status_code input for list_buyers_by_status.
No input parameters required.
{
"type": "object",
"fields": {
"statuses": "array of objects each containing code (string) and name (string)"
},
"sample": {
"data": {
"statuses": [
{
"code": "4",
"name": "Publicadas"
},
{
"code": "5",
"name": "Propostas abertas"
},
{
"code": "6",
"name": "Em disputa"
},
{
"code": "7",
"name": "Em homologação"
},
{
"code": "8",
"name": "Concluídas"
}
]
},
"status": "success"
}
}About the licitacoes-e.com API
The Licitacoes-e API exposes 3 endpoints covering Brazilian public procurement data from the Banco do Brasil platform. Use list_all_statuses to retrieve all valid tender status codes and names, list_buyers_by_status to see which government buyers have active tenders under a given status, and get_tender_details to pull the full record for a specific tender by its unique ID.
Tender Statuses and Buyer Data
The list_all_statuses endpoint returns an array of status objects, each with a code and name field. These codes map to the tender lifecycle stages available on the Licitacoes-e platform — for example, code 4 corresponds to "Publicadas" (published) and code 6 to "Em disputa" (under dispute). The status codes returned here are the accepted inputs for list_buyers_by_status, making this a natural first call when building any workflow that filters by procurement stage.
Querying Buyers by Status
list_buyers_by_status accepts a status_code parameter (e.g. '4', '5', '6', '7') and returns one row per buyer–sub_status combination. Each row includes buyer_id, buyer_name, sub_status_code, sub_status_text, tender_count, and display_text. The response also includes main_status_code and total_buyer_rows for quick summary counts. Some status codes may return empty results depending on live procurement activity at query time.
Tender Detail Records
get_tender_details takes a tender_id (the "Nº Licitação" identifier, e.g. '1055555') and returns a details object containing key-value pairs from the tender's full record — covering fields such as deadlines, procurement modality, and bid information. Note that this endpoint is subject to reCAPTCHA protection on the source site, which can affect availability and response consistency.
- Monitor which government buyers have the most active tenders in the 'Em disputa' stage using tender_count from list_buyers_by_status.
- Build a tender alert dashboard by polling list_buyers_by_status across multiple status codes and tracking changes in buyer activity.
- Retrieve full procurement details for a known tender ID using get_tender_details to extract deadlines and bid information.
- Aggregate sub_status distributions across buyers to analyze the volume of tenders at each procurement stage.
- Map buyer_id values to procurement activity levels for vendor prospecting and public contract analysis.
- Seed a local database with all valid status codes via list_all_statuses to normalize tender lifecycle data in downstream applications.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.