- Removed lines and positions
Creating a tender
Carrying your own reference and routing
Reading tenders
Tender documents
Editing a tender
Closing a tender
Acknowledging a tender
Reporting lifecycle events
Completion feed
Public Tenders Create
Public Tenders List
Public Tenders Get
Public Tenders Update
Public Tenders List Documents
Public Tenders Acknowledge
Public Tenders Record Event
Removed lines and positio...
By default a tender contains only what is currently on it: a line removed after you imported the tender simply stops appearing, which leaves you unable to tell it apart from one that never existed. Pass include_deleted=true on GET /tenders or GET /tenders/{tender_id} and removed lines come back flagged instead of omitted, so you can delete the corresponding record in your own system:
is_deletedistrueon the removed line anddeleted_atcarries the UTC time that line was removed (nullon a legacy row removed before those times were recorded).- Removals are reported per line. Take one article off a position and that article comes back flagged next to the position's live lines — which is what you need if you keep one record per matched article. The
idtells you which record to drop. - A whole position (Ordnungszahl) is gone exactly when all lines sharing its
position_numbercome back flagged. If you key your records on the ordinal number rather than per article, that is your signal; a position with at least one unflagged line still exists. - Removed lines never count toward
totals, and theETagcovers the live content only. A document fetched withinclude_deleted=truetherefore round-trips throughPATCH /tenders/{tender_id}unchanged: echoed removed lines are ignored. - A position that Mercura merely flags as not relevant is not a removal and stays hidden either way.
- Line
ids are stable across a removal — the live primary line keeps its handle. They do change when a source document is reprocessed, which recreates the tender's positions and lines (and changes theETag).