canonical: https://jentic.com/apis/search.dip.bundestag.de/search-dip-bundestag

# Search Dip Bundestag De Bundestag API

API for accessing documents, proceedings, and parliamentary data from the German Bundestag's Documentation and Information System (DIP). The API exposes 16 endpoints secured with apiKey authentication.

## For AI agents

Programmatically list printed papers (drucksachen), get a specific printed paper. Covers 16 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- List printed papers (Drucksachen)
- Get a specific printed paper
- Integrate Bundestag API into automated workflows
- Query and filter Bundestag API records by parameters
- Monitor Bundestag API operational status and events

## Use cases

### Developer Tools Operations

Use the Bundestag API to perform developer tools operations programmatically. The API provides 16 endpoints covering core functionality including list printed papers (drucksachen), get a specific printed paper, list printed papers with full text.

Example prompt: Call GET /drucksache to list printed papers (drucksachen)

### Automated Aktivitaet Management

Automate aktivitaet operations by combining multiple Bundestag API endpoints. Agents can get a specific printed paper and then list printed papers with full text in a single workflow.

Example prompt: Call GET `/drucksache/{id}` to get a specific printed paper, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Bundestag API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'list printed papers (drucksachen)', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/drucksache` | List printed papers (Drucksachen) |
| GET | `/drucksache/{id}` | Get a specific printed paper |
| GET | `/drucksache-text` | List printed papers with full text |
| GET | `/drucksache-text/{id}` | Get full text of a specific printed paper |
| GET | `/plenarprotokoll` | List plenary protocols |
| GET | `/plenarprotokoll/{id}` | Get a specific plenary protocol |
| GET | `/plenarprotokoll-text` | List plenary protocols with full text |
| GET | `/plenarprotokoll-text/{id}` | Get full text of a specific plenary protocol |

## Key resources

- **Aktivitaet** — Operations for aktivitaet
- **Drucksache** — Operations for drucksache
- **Drucksache Text** — Operations for drucksache text
- **Person** — Operations for person
- **Plenarprotokoll** — Operations for plenarprotokoll

## Why Jentic

- **Setup:** Wiring the Bundestag API by hand means passing your apikey in the query string against search.dip.bundestag.de, tracking paging across its document and protocol endpoints, and building your own retry handling. Through Jentic you install once, import the Bundestag API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Bundestag API exposes read-only lookups over printed papers, plenary protocols, and legislative proceedings, so you limit the agent to the operations it needs, such as listing drucksachen or fetching one by id. You choose the operations it may call, and any you leave out stay unavailable to the agent.
- **Credential handling:** Your Bundestag API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list printed papers (drucksachen)' or 'fetch a plenary protocol by id', and Jentic returns the matching Bundestag API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Bundestag API use?

The Bundestag API uses an API key passed in the `apikey` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list printed papers (drucksachen) with the Bundestag API?

Yes. Use the GET /drucksache endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Bundestag API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list printed papers (drucksachen) through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list printed papers (drucksachen)'. Jentic returns the matching Bundestag API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Bundestag API have?

The Bundestag API exposes 16 endpoints covering aktivitaet, drucksache, drucksache text operations.

### Can I limit what my agent is allowed to do with the Bundestag API?

Yes. The Bundestag API exposes only read-only lookups over printed papers (Drucksachen), plenary protocols, and legislative proceedings, and because you run Jentic One self-hosted, your own rules decide which of those operations the agent may call. You can allow just listing Drucksachen or fetching one by id, for example, and leave every other operation unavailable to the agent. The API key stays under your control and is injected at execution time, so the agent only ever reaches the endpoints you have permitted.