e-Vergabe Tender Scraper
Pricing
from $1.00 / 1,000 results
Go to Apify Store
e-Vergabe Tender Scraper
Scrape e-Vergabe procurement notices. Search and collect record details. Export available fields to Excel, CSV or JSON.
Pricing
from $1.00 / 1,000 results
Rating
0.0
(0)
Developer
ScrapingMonkey
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Features
Limited permissions
Share
Extract e-Vergabe procurement notices for tender discovery, buyer research and procurement monitoring. e-Vergabe Tender Scraper collects public information into one complete dataset table, ready to export as Excel, CSV or JSON.
Use search filters or individual public record links, set how many results you need and start the Actor. Search finds matching records; Details retrieves the available information for records you already know.
| At a glance | Details |
|---|---|
| 📥 Input | Search filters or individual public record links |
| 📋 Collection modes | Search tender records; Get tender details |
| 📤 Output | One row per record, or a failed row for an unsuccessful input |
| 📄 Pagination | Automatic, up to maxResults while more records are available |
| 🔐 Website login | Not required |
| 💾 Export | One dataset view with all fields; Excel, CSV and JSON |
What the e-Vergabe scraper collects 📋
| Mode | What you receive |
|---|---|
| Search tender records | Matching procurement notices and the fields published in the search results. |
| Get tender details | Available public information for each supplied record. The full output example below shows its actual fields. |
The field table and complete examples below show the information this Actor returns. Optional values depend on what the source publishes for the selected record.
Coverage for this Actor:
- Search Germany’s federal e-Vergabe procurement notices by keywords.
- Public notice descriptions, contracting authorities and deadlines are available. Participation and some tender documents may require registration.
How to scrape e-Vergabe 🚀
- Choose Search tender records or Get tender details.
- Complete the search filters or individual public record links.
- Set Maximum results. The minimum is 1.
- Start the Actor and review the saved dataset.
- Export the results or connect them to your workflow.
Search tender records — input example
Get tender details — input example
maxResults limits all saved rows for each search or supplied record, including a failed row. It does not guarantee that the source has that many matching records. A detail lookup normally returns one record, although sources with multiple revisions or establishments can return more.
e-Vergabe data fields and complete output 📦
Each result stays in one row. Every returned field appears in the same dataset view, including list fields and additional published facts. Fields unavailable for a particular record remain empty.
| Field | Included data |
|---|---|
result_type | Selected collection mode. |
input | Submitted search settings, record link or record number. |
status | Collection outcome. |
error_code | Failure category for an unsuccessful input. |
error_message | Readable explanation for an unsuccessful input. |
record_id | Stable public notice or tender-lot identifier. |
url | Public source notice link. |
title | Published notice title. |
reference | Published reference number. |
buyer | Contracting authority or procuring organisation. |
location | Place of performance or published region. |
procedure | Procurement procedure name. |
deadline | Submission deadline with the advertised time zone. |
published_at | Source publication date and time. |
additional_fields.name | Names of additional published fields, when present. |
additional_fields.value | Their corresponding values in the same order. |
record_data.name | Record data / name, when published. |
record_data.value | Record data / value, when published. |
description | Public description or summary of the notice. |
notice_text | Full public notice content in readable text. |
documents_and_links.title | Documents and links / title, when published. |
documents_and_links.url | Documents and links / url, when published. |
email_addresses | Public procurement contact email addresses. |
The complete result below is included for every mode. Text and lists are not shortened. These are examples from validation runs; the source can change.
Search tender records — complete JSON result
Get tender details — complete JSON result
Input settings ⚙️
| Setting | What to enter |
|---|---|
What to collect (mode) | Choose the information you need. |
Maximum results per search or link (maxResults) | Collect up to this many saved results for each search or record link. Minimum: 1. |
Procurement keywords (keyword) | Words in the procurement title or notice. Leave blank to browse current results. |
Tender links (recordUrls) | Paste one individual public record link per line. Use this field in Details mode. |
e-Vergabe scraping use cases 🎯
Build a tender or contract shortlist
Search the supported procurement collection and export matching records. Keep deadlines, buyer names and original references together when reviewing opportunities.
Research public buyers
Compare available buyer, supplier and contract information across records. Preserve the published currency and value type when working with amounts.
Monitor published procurement records
Schedule repeated exports and compare stable record IDs to identify newly published notices and changes. A search result is not confirmation that bidding remains open.
Pricing and saved-result behavior 💰
See the Actor’s Pricing tab for the current rate. Under dataset-item pricing:
- Each saved record is one result. Lists and additional details attached to it do not create extra rows.
- A saved
failedrow is also one billable dataset item. This includes invalid inputs, unavailable records, empty searches and exhausted retries. - At most one failed row is saved per input. Retry attempts do not create additional dataset rows.
maxResultscaps all saved rows for the input. Duplicate copies of the same input are processed once.
e-Vergabe scraper API and integrations 🔌
Replace $ACTOR_ID with the ID shown in the Actor’s API tab and $APIFY_TOKEN with your Apify token.
Use Apify schedules for recurring collection, webhooks for completion notifications, and integrations for Google Sheets, Make, Zapier, cloud storage or your own application.
Reliability and public-data limits ⚠️
Temporary request failures are retried up to five total attempts. Invalid record inputs save a failed row without a website request. Confirmed missing records are not retried unnecessarily. If a later request fails, records already saved remain in the dataset. Normal pagination completion does not add a failed row. Collection stops after two consecutive pages return no new records. Configuration, data-saving or request-scheduling failures stop the run.
e-Vergabe controls the available records and fields. Search records can contain less information than a full public card. The Actor preserves published values and does not fill missing facts with estimates.
Frequently asked questions ❓
Do I need a e-Vergabe account?
No. This Actor collects the supported public information without your website login.
Which search filters can I use?
The input form supports procurement keywords. Only the displayed filters are supported.
How many records can I collect?
Set maxResults to the maximum saved rows you want for each input. The minimum is 1. Collection can finish earlier when the source runs out of results or stops returning new records.
Why are some fields empty?
The source may not publish a value for that record or mode. Optional information remains empty.
Can I export all the fields?
Yes. All returned fields are included in one dataset view. Nested lists remain attached to their parent record.
Support 🛟
For a reproducible issue, share the run ID, selected mode and a safe public example through the Actor’s support channel. Keep tokens, passwords and proxy credentials private.
