# Oeffentliche Vergabe German Tenders API

> German public tenders: 19,000+ active lots from the federal publication service, with notice details

- Vendor: `oeffentlichevergabegermantende` · version 1.0 · category Government Data · tags german tenders api, germany procurement api, public tenders api, ausschreibungen api, eforms notices api, oeffentliche vergabe api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/oeffentlichevergabegermantende
- This document: https://apiclay.com/docs/oeffentlichevergabegermantende.md
- OpenAPI 3.1: https://apiclay.com/api/oeffentlichevergabegermantende/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `oeffentlichevergabegermantende`
- Updated: 2026-11-18

## About

## Oeffentliche Vergabe German Tenders API

The search of Öffentliche Vergabe, Germany's federal publication service for public procurement notices: active tender lots of federal, state and municipal buyers, searchable by free text, notice type and other fields, each with notice and lot title, buyer, main CPV code, nature (works, supplies, services), places of performance with NUTS code, deadlines and publication date; and the full eForms notice with procedure, lots, award criteria, organisations and TED publication.

Data comes from **oeffentlichevergabe.de** (https://oeffentlichevergabe.de). Every route calls the source's own public API and returns it unchanged.

Typical flow: POST `/search` with the sample body (change the free text and `PAGE`), then `/notice?id=¬iceVersion=01`.

### Routes

#### POST `/search` - Search lots
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| SELECT | body | string | yes | `ALL`. |
| WHERE | body | array | yes | Conditions `{"fields": [...], "operator": ..., "operands": [...]}`. Free text: `{"fields": ["allFreeText"], "operator": "MATCH_ALL", "operands": ["Software"], "negate": false}`; the sample also keeps active (`active` = true) contract notices (`noticeType` IN ...). |
| FROM | body | string | yes | `lots`. |
| PAGE | body | object | yes | `{"number": 0, "size": 25}`. |
| ORDER | body | object | no | e.g. `{"field": "publicationDate", "direction": "DESC"}`. |

Returns: `totalElements`, `offset`, `elements`: `noticeIdentifier`, `noticeVersion`, `noticeTitle` and `lotTitle` (per language), `lotIdentifier`, `procedureIdentifier`, `noticeType`, `mainNature`, `mainCpvCode`, `buyers`, `placesOfPerformance` (`country`, `nutsCode`, `city`), `deadlineReceiptTenders`, `publicationDate`, `strategicProcurement`.

#### GET `/notice` - Notice
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| id | path | string | yes | `noticeIdentifier` from `/search`. |
| noticeVersion | query | string | yes | `noticeVersion` from `/search`, e.g. `01`. |

Returns: The eForms notice as JSON: `noticeType`, `noticeSubType`, `procedure`, `purpose`, `lots`, `classification`, `buyers`, `organisation` and `organisationRoles`, `placeOfPerformance`, `procedureLegalBasis`, `exclusionGrounds`, `tedPublication`, `procurementPlatform`, `publicationDate`. About 60 KB.

### Caveats

- Notices give the buyer's contact point, often a named officer with email and phone, as published.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by oeffentlichevergabe.de.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### POST /search — Search lots
- Gateway: `POST https://api.apiclay.com/v1/api/oeffentlichevergabegermantende/search`
- Body sample (JSON):

```json
{"SELECT": "ALL", "WHERE": [{"fields": ["allFreeText"], "operator": "MATCH_ALL", "operands": ["Software"], "negate": false}, {"fields": ["active"], "operator": "=", "operands": [true]}, {"fields": ["noticeType"], "operator": "IN", "operands": ["pin-cfc-standard", "qu-sy", "cn-standard", "subco", "cn-desg", "pin-cfc-social", "cn-social"]}], "FROM": "lots", "PAGE": {"number": 0, "size": 5}, "ORDER": {"field": "publicationDate", "direction": "DESC"}}
```

- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /notice — Notice
- Gateway: `GET https://api.apiclay.com/v1/api/oeffentlichevergabegermantende/notice`
- Public query params: `noticeVersion` (string, required), `id` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X POST "https://api.apiclay.com/v1/api/oeffentlichevergabegermantende/search" \
  -H "token: <YOUR_APICLAY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"SELECT": "ALL", "WHERE": [{"fields": ["allFreeText"], "operator": "MATCH_ALL", "operands": ["Software"], "negate": false}, {"fields": ["active"], "operator": "=", "operands": [true]}, {"fields": ["noticeType"], "operator": "IN", "operands": ["pin-cfc-standard", "qu-sy", "cn-standard", "subco", "cn-desg", "pin-cfc-social", "cn-social"]}], "FROM": "lots", "PAGE": {"number": 0, "size": 5}, "ORDER": {"field": "publicationDate", "direction": "DESC"}}'
```

Index of every published API: https://apiclay.com/llms.txt
