- Document feed
Creating a tender
Carrying your own reference and routing
Reading tenders
Line order
Removed lines and positions
The complete Leistungsverzeichnis
Review notes (
Tender documents
Editing a tender
Closing a tender
Acknowledging a tender
Reporting lifecycle events
Completion feed
Export file
Public Tenders Create
Public Tenders List
Public Tenders Document Feed
Public Tenders Get
Public Tenders Update
Public Tenders List Documents
Public Tenders Get File
Public Tenders Acknowledge
Public Tenders Record Event
Document feed
GET /tenders/documents returns the same documents for all tenders of your organisation as a cursor-paginated feed ordered by (updated_at, id) — the same modified_since / cursor / limit contract as GET /tenders. Poll it to archive documents without walking every tender:
GET /tenders/documents?modified_since=2026-10-13T08:00:00ZA document comes back whenever its record changes:
- it was uploaded — also after the tender was first handed over;
- a user edited its document custom fields (e.g. moved it to another archive folder);
- a user asked for it to be sent to the ERP again (
erp_export_requested_atmoved).
Internal processing can touch a document as well, so treat an appearance as "look again", not as "archive again": decide by id together with erp_export_requested_at and custom_fields whether to file it anew. Page with next_cursor until it is null, then keep the last updated_at as your next modified_since.