AEC Tenders icon

AEC Tenders

Fetches public construction tenders from Brazil's PNCP

Actions4

Overview

The "AEC Tenders" node fetches public construction tender data from Brazil's PNCP (National Public Procurement Portal). Specifically, the Search by Keyword operation allows users to search tenders published within a specified date range that contain certain keywords in their descriptions. This is useful for professionals and companies looking to find relevant public construction projects based on specific interests or expertise areas.

Typical use cases include:

  • Construction firms searching for upcoming projects involving engineering, renovation, or infrastructure.
  • Consultants tracking tenders related to sustainable or environmental projects.
  • Suppliers monitoring procurement opportunities matching particular contract objects.

For example, a user could search for tenders published between January 1, 2025, and December 31, 2025, containing keywords like "engenharia, construção, reforma" to find relevant contracts in those fields.

Properties

Name Meaning
Start Date The start date of the search period in YYYY-MM-DD format (e.g., 2025-01-01). Required.
End Date The end date of the search period in YYYY-MM-DD format (e.g., 2025-12-31). Required.
Keywords Comma-separated list of keywords to search for in tender descriptions (e.g., engenharia, construção, reforma). Required.
Return All Boolean flag indicating whether to return all matching results or limit the output.
Limit Maximum number of results to return if "Return All" is false. Minimum value is 1. Default is 50.

Output

The node outputs an array of JSON objects representing tenders matching the keyword search criteria. Each tender object includes detailed standardized fields such as:

  • pncpId: Tender unique identifier.
  • procuringEntityName: Name of the procuring entity.
  • procuringEntityCNPJ: CNPJ (tax ID) of the procuring entity.
  • tenderObject: Description of the contract object.
  • tenderModality: Type/modality of the tender.
  • tenderSituation: Current status of the tender.
  • publicationDate: Date when the tender was published.
  • proposalOpeningDate: Date when proposals will be opened.
  • estimatedTotalValue: Estimated total contract value in BRL.
  • municipalityCode and municipalityName: Location details.
  • stateCode and stateName: State information.
  • legalProcedure, process, and other legal/administrative details.
  • portalUrl: Direct URL to the tender on the PNCP portal.
  • Additional metadata such as risk score, data quality assessment, urgency level, and category classification.

This structured output enables easy filtering, reporting, or integration with other systems.

Dependencies

  • Requires access to the PNCP public API endpoint (https://pncp.gov.br/api/consulta).
  • Needs an internet connection to make HTTP requests.
  • No explicit API key or authentication token is required according to the code, but network connectivity and API availability are essential.
  • The node uses standard HTTP headers including a custom User-Agent and request ID for traceability.

Troubleshooting

Common Issues

  • Empty or no results: Ensure the date range and keywords are correctly specified and that there are tenders matching those criteria.
  • Invalid date formats: Dates must be valid and in the correct format (YYYY-MM-DD).
  • Missing keywords: Keywords parameter is mandatory for this operation.
  • API rate limiting: The PNCP API enforces rate limits; excessive requests may result in temporary blocking.

Error Messages and Resolutions

  • "Keywords are required for search": Provide at least one keyword separated by commas.
  • "Start date and end date are required for keyword search": Both dates must be set.
  • "PNCP API Error (RATE_LIMIT_EXCEEDED): Limite de requisições excedido": Too many requests; wait the specified retry time before retrying.
  • "Timeout na consulta à API PNCP": Request took too long; try reducing the date range or try again later.
  • "Não foi possível conectar à API PNCP": Network connectivity issue; check your internet connection.
  • "Operation "searchByKeyword" is not supported": This would indicate a misconfiguration; ensure the operation name is correct.

Links and References

Discussion