GET /api/2/notice/submission/info/{submission_id}
For version 1 of this method, see GET /api/1/notice/submission/info/{submission_id}. Version 1 of this method is deprecated, but we still support it for now to provide backwards compatibility and we encourage the use of version 2 of this method instead. Version 2 also provides the ocid as part of response json whereas version 1 does not.
Gets notice information for a published or non published notice as a NoticeInformation object.
Requires Authorization
The endpoint requires a Basic Auth in the http authorization header. For details, please see the Authentication section.
Request Information
URI Parameters
Name | Description | Type | Format | Max length | Example |
---|---|---|---|---|---|
submission_id |
The submission id received when the notice was submitted |
string |
yyyymmdd-nnnnnn |
15 |
20250430-123456 |
publication_number |
The publication number of the notice |
string |
nnnnnn-yyyy or yyyynnnnnn |
11 |
123456-2025 or 2025123456 |
Body Parameters
None.
Request Formats
GET
/api/latest/notice/submission/info/20250430-123456
Response Information
Resource Description
A NoticeInformation object containing details of the notice status.
Response Formats
In the case of successful response a NoticeInformation object is returned in JSON format.
Version 2 changes:
- Adds new variable, OCID, into publication info.
application/json, text/json
{ "submission_id": "20250430-000050", "received_at": "2023-09-15T08:10:04Z", "status": "RECEIVED", "reason_code": null, "status_updated_at": "2023-09-15T08:10:04Z", "no_doc_ext": null, "form": null, "languages": [], "publication_info": { "ojs_number": "000", "no_doc_ojs": "2023/S 000-002015", "publication_date": "2023-09-12 15:45:35", "truk_links": { "EN": "https://www.find-tender.service.gov.uk/Notice/002015-2023" }, "ocids": [ "ocds-h6vhtk-123456", "ocds-h6vhtk-789101" ] }, "technical_validation_report": null, "validation_rules_report": null, "quality_control_report": null, "ref_submission_id": null, "ref_no_doc_ojs": null }
In the case the wrong parameter name provided.
application/json, text/json
{ "timestamp": "2018-01-05T08:51:38Z", "status": 400, "error": "Bad Request", "message": "Request parameters unknown", "path": "/api/latest/notice/submit", "exception": "Request parameter 'notices' is not recognised, no parameter expected" }
In the case the Accept header is provided and set with a value different than ‘application/json’.
application/json, text/json
{ "timestamp": "2017-01-10T10:03:30Z", "status": 406, "error": "Not Acceptable", "message": "Not acceptable value for ‘Accept’ header. Only ‘application/json’ format is supported", "path": "/api/latest/notice/submission/info/20250430-000004" }
In the case the related notice could not be found.
application/json, text/json
{ "timestamp": "2017-01-10T10:03:30Z", "status": 404, "error": "Not Found", "message": "Notice not found", "path": "/api/latest/notice/submission/info/20250430-000004" }