- Public Tenders Acknowledge
Report the ERP/CRM import outcome for one tender.
The partner POSTs status (SUCCESS / FAILED), optionally an external_id (its own offer/record id) and metadata, and a message (required on FAILED as the reason, optional on SUCCESS as a free-text note). Idempotent and latest-wins: a later acknowledgement overwrites the earlier one. When supplied, external_id is also written back to the tender's erp_offer_id. Returns the recorded acknowledgement (status, sticky-aware external_id, message, metadata, acknowledged_at) — the same shape as the acknowledgement field on PublicTenderOut, not the whole tender. Recording-only: it does not alter the tender's lifecycle status or re-trigger any export.
Outcome a partner reports after importing a tender's offer into their ERP/CRM.
Translated from the internal RequestAckStatus via tenders.service._TENDER_ACK_STATUS_MAP. A separate axis from PublicTenderStatus: that is Mercura-side lifecycle, this is the partner's import result.
Partner-side ERP/CRM id of the created offer / record. Typically set on SUCCESS.
Free-text note about the outcome. Required when status is FAILED (the failure reason); optional on SUCCESS.
- Mock serverhttps://docs.mercura.ai/_mock/openapi/tenders/{tender_id}/acknowledgements
- https://docs.mercura.ai/api/public/v1https://docs.mercura.ai/api/public/v1/tenders/{tender_id}/acknowledgements
- Productionhttps://prod-euapi.mercura.ai/api/public/v1/tenders/{tender_id}/acknowledgements
curl -i -X POST \
'https://docs.mercura.ai/_mock/openapi/tenders/{tender_id}/acknowledgements' \
-H 'Content-Type: application/json' \
-H 'authorization: string' \
-d '{
"external_id": "AB-2026-5567",
"message": "Angebot in ERP angelegt.",
"metadata": {
"erp_document": "AB-2026-5567",
"warehouse": "Z-100"
},
"status": "SUCCESS"
}'Successful Response
Outcome a partner reports after importing a tender's offer into their ERP/CRM.
Translated from the internal RequestAckStatus via tenders.service._TENDER_ACK_STATUS_MAP. A separate axis from PublicTenderStatus: that is Mercura-side lifecycle, this is the partner's import result.
Partner-side ERP/CRM id of the created offer / record, when provided.
Free-text note about the outcome. On FAILED this is the failure reason (required); on SUCCESS an optional note.
Optional extra references / raw payload the partner echoed back for traceability.
{ "erp_document": "AB-2026-5567", "warehouse": "Z-100" }
{ "acknowledged_at": "2026-07-09T12:00:12Z", "external_id": "AB-2026-5567", "message": "Angebot in ERP angelegt.", "metadata": { "erp_document": "AB-2026-5567", "warehouse": "Z-100" }, "status": "SUCCESS" }