redflags.eu

What It Is

RedFlags API has a very clear positioning: it provides the notices and organization data collected by the RedFlags project in a structured, machine-processable JSON format for systems beyond the website. It is not a general-purpose development framework, but a query-oriented API for public procurement and notice data. Calls are made via HTTP GET, with query parameters placed in the URL, and response data returned in the result field of the JSON payload.

Core Capabilities

According to the documentation, the API mainly offers four types of endpoints: /notice for querying a single notice, /notices for querying a list of notices, /organization for querying a single organization, and /organizations for querying a list of organizations. The notice list endpoint supports a relatively rich set of filters, including buyer name, CPV code, date range, document type, number of red flags, indicator name, text content, value range, and winning bidder name. List endpoints support pagination through count and page, and return first, last, prev, and next in the links object, making client-side pagination straightforward.

Integration and Documentation

Access requires registration and a unique API Key, which must be included in each request via the access_token parameter. The documentation describes the structure of informational messages and error messages; error objects include the HTTP status code, summary, details, and the source parameter of the error, which is helpful for development and debugging. However, the documentation does not show complete response examples, nor does it provide OpenAPI/Swagger specs, SDKs, multilingual code examples, a versioning policy, rate-limit rules, or data update frequency information. As production-grade integration material, it is still somewhat brief.

Pricing and Deployment

The crawled text does not disclose pricing, free quotas, commercial licensing, or payment methods, nor does it clarify whether the service is open source or closed source, or whether self-hosting is available. As a result, it is not possible to assess the cost model or feasibility for enterprise deployment. Teams that need a stable long-term integration should contact [email protected] before registration to confirm access rights, request limits, data licensing, and service availability.

Pros, Cons, and Who It Is For

The strengths are its simple interface, clearly defined data domain, and practical filtering dimensions. It is suitable for compliance research, procurement risk analysis, data journalism, academic research, or integration into internal data pipelines. The drawbacks are the lack of ecosystem information, no SDKs or integration guides, and limited platform-level capabilities. The source text does not provide information on access from China, so network connectivity, registration email deliverability, and payment availability cannot be assessed. If access is unstable, consider using local caching or looking for local public procurement data sources as alternatives.