Overview

The Tenders in Poland API provides structured access to Polish government procurement notices and contract awards from tenders.guru, covering public sector buyers across all regions of Poland. It requires no API key and returns clean JSON data suitable for analysis, dashboards, or transparency reporting. Developers can filter by date, category, or value to find relevant tenders quickly.

Beginner Tip

Start by fetching the first page of results with https://tenders.guru/pl/api/tenders?page=1 — the response includes pagination metadata so you can iterate through all available tenders systematically.

Available Data

The kind of data this API exposes, based on its documentation. We could not call the endpoint to confirm the exact field names.

Tenders in Poland data via REST API

Example Response

Illustrative shape only — we were not able to call this endpoint (it requires credentials or exposes no public sample URL), so the fields below show the kind of data this API returns rather than a recorded response.

JSON Response · Illustrative
{
  "status": "success",
  "data": {
    "result": "Data from Tenders in Poland",
    "description": "Get data for procurements in Poland in JSON format",
    "timestamp": "2025-01-15T10:00:00Z"
  }
}

Field Reference

id Unique identifier for the tender record
title Subject or name of the procurement tender
buyer Public entity or government body issuing the tender
value Estimated or awarded contract value in PLN
date Publication or award date of the procurement notice
supplier Winning company or supplier name, when contract is awarded

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://tenders.guru/pl/api/tenders?page=1&per_page=10";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

429 Too Many Requests Hitting the API too frequently in a loop without delays
Throttle your requests to 1 per second and store results in a local database or file
Unexpected JSON structure Assuming the response shape matches another tenders.guru country without checking
Always inspect the actual response first with curl or Postman before writing parsing logic
Network timeout Large result pages taking too long to load on slow connections
Use a smaller per_page value such as 10 or 25 to reduce payload size

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS UNKNOWN
Category Business
Difficulty Beginner
Listing details not endpoint-verified

Related Tags

Similar APIs

View All →