- Closing a tender
Creating a tender
Carrying your own reference and routing
Reading tenders
Removed lines and positions
Tender documents
Editing 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
Closing a tender
Not every tender that reaches Mercura is worked in Mercura. A small one may be quoted by hand, or it may belong to a product line that is not onboarded — and its case is then closed in your CRM while the tender stays open in Mercura forever. Left alone, those accumulate until the open list is unusable.
Send status: "CANCELLED" to close such a tender so it leaves the open inbox:
PATCH /tenders/63365
{ "status": "CANCELLED" }CANCELLEDis the only writable transition. Everything else is Mercura-side workflow — a tender becomesDONEby being exported, andNEW → IN_PROGRESSwhen someone starts working it. Any other target is a400.- Echoing the current status is a no-op, so a full GET body still round-trips through PATCH whatever the tender's status is.
409forPARSINGandDONE. APARSINGtender is mid-flight (retry once it lands); aDONEone has already been completed in Mercura, and silently downgrading that toCANCELLEDwould lose the result. Everything else —NEW,IN_PROGRESS,PARSING_FAILED— is cancellable.- Cancelling is not an acknowledgement. Use
POST /tenders/{tender_id}/acknowledgementsto report an import outcome; use this to close a tender nobody will work.