- Acknowledging a tender
Creating a tender
Carrying your own reference and routing
Reading tenders
Removed lines and positions
Tender documents
Editing a tender
Closing 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
Acknowledging a tender
POST /tenders/{tender_id}/acknowledgements— after you import a tender's offer into your ERP/CRM, report the result back so the Mercura operator can see it. Sendstatus: "SUCCESS"(optionally with your ownexternal_id, a free-textmessage, and anymetadata), orstatus: "FAILED"with a requiredmessagedescribing why. The call is idempotent and latest-wins for the status and message (a retry that first failed then succeeded ends upSUCCESS); a once-reportedexternal_idis kept even if a later acknowledgement omits it. Yourexternal_idis also written back to the tender'serp_offer_id, so it shows up everywhere Mercura reads that field. The response body is the recorded acknowledgement only —{ status, external_id, message, metadata, acknowledged_at }, the same shape as the tender'sacknowledgementfield — a small deterministic confirmation of what Mercura persisted (including the stickyexternal_id) without refetching the whole tender. Recording-only: it does not change the tender's lifecyclestatusor re-trigger an export.